On 3/22/07, Richard Hughes <[EMAIL PROTECTED]> wrote:
On 22/03/07, Rob Taylor <[EMAIL PROTECTED]> wrote:
> Umm, i was actually talking about context switches, nothing to do with
> async versus sync. I'd expect an app to do async calls on startup.
> I guess its theoretically possible at the libdbus level to queue up a
> number of messages and do one context switch to send them all...
Gotcha. What about doing both?
We keep the CanSuspend for the trivial desktop case, and also provide
a GetCapabilities method that returns a bitfield for embedded use, or
for languages like python that can unwrap a bitfield easily.
It's one extra method, and one extra signal, so it's hardly much API
duplication.
Disagreed. I'd rather keep one GetCaps that can be called by a wrapper
library (thing glib and stuff) on startup and cached so later that
*wrapper* can provide you with individual CanDoSomething wrappers.
This would reduce the bus traffic and remove the requirement of
caching the values on the application side.
--
Patryk Zawadzki
Generated Content
_______________________________________________
xdg mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/xdg
