[Bug 21180] Decide where a{sv}s are needed for future expansion of clients

[bugzilla-daemon at freedesktop.org]

http://bugs.freedesktop.org/show_bug.cgi?id=21180





--- Comment #1 from Simon McVittie <simon.mcvittie at collabora.co.uk>  2009-04-17 10:41:57 PST ---
Possible places we might want an a{sv} for future expansion:

* Observer.ObserveChannels: we already have Observer_Info

* Approver.AddDispatchOperation: if we turn the expansion things into immutable
properties of the channel dispatch operation, then we're fine; the only problem
is if their values can change, in which case either we use an InitialFoo hack
(and don't allow the value to change until ADO has returned so the client has
time to connect to signals), or the client calls back to the dispatch operation
to get the initial value just after connecting to signals. Neither is a huge
burden, so I don't think an a{sv} is necessarily needed.

* Handler.HandleChannels: we don't have a Handler_Info but IMO we should add
one

* Handler.Interface.RequestNotification.AddRequest: we pass in exactly the
request and its immutable properties, which we can always add to later; same
considerations as A.ADO above.

Relatedly, ChannelRequest doesn't have an Interfaces property; for future
expansion, perhaps it should. If so, MC should pass it in all the usual dicts
of immutable properties.


-- 
Configure bugmail: http://bugs.freedesktop.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.