[vlc-devel] Re: [bmpx] Re: Re: [bmpx] Re: [Banshee-List] [bmpx] Re: Proposal for a common D-Bus interface for media players

Milosz Derezynski internalerror at gmail.com
Thu Dec 7 19:23:06 CET 2006

There is really no pratical problem with handing over an interface from one
app to another; i don't want to go into tech/code details right now until
it's neccessary, but it is generally not a problem at all when done right,
no matter how huge the latency is.

There should be some crash dection etc, perhaps, maybe similar to BMP's
sentinel daemon which watches the main, and currently only, interface come
and go, and if the interface should just "disappear", without bmpx signing
off (ShutdownComplete signal on dbus with no args), it will report a crash;
we have a similar crash detection on startup; it's not very different from
let's say bug-buddy, just that the process is not run as a child process.

On 12/7/06, Peter Stuge <stuge-xmms2 at cdy.org> wrote:
> On Thu, Dec 07, 2006 at 04:53:51AM -0500, William Pitcock wrote:
> > - What if the user wants to switch his preferred media player from
> >   Amarok to BMPx, Videolan, Audacious or XMMS2?
> >
> >   + We could send a signal to the other player saying that it is OK
> >     to takeover the common interface, but if an application is slow
> >     to release the interface, the other player may not successfully
> >     bind to the org.freedesktop.MediaPlayer instance like desired.
> Does DBUS support bus mastering/bus sharing like some other buses? In
> that case it just uses timeouts.
> (Yes, I know it's not a hardware bus.)
> //Peter
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.videolan.org/pipermail/vlc-devel/attachments/20061207/0e55577d/attachment.html>

More information about the vlc-devel mailing list