On Sun, Jun 04, 2006 at 09:37:46PM -0500, David Berg wrote: > On 6/4/06, Jonathan Matthew <[EMAIL PROTECTED]> wrote: > >Armed with my lack of knowledge of your setup, I'm going to suggest > >running rhythmbox in a stripped down session for some user inside a vnc > >server, so your other users can connect to that to control it. I'm not > >sure of the best way of setting this up, or which of the 37 different > >vnc servers is best to use. > > This may work, but seems like an awful lot of hassle. I guess I would > like to see something like a rhythmbox daemon and rhythmbox clients. > Allowing a user to select who can control the daemon and that would > also make streams available over the network yet keep accounting > information on song popularity. > > > Is this clearer?
Yes, but one of those options is possible today with five minutes of reading documentation and writing trivial scripts, and the other would take a serious amount of development work and won't be available any time soon. I don't think anyone is arguing that it's not a good idea, but no one is really working on it. Another (uglier) option would be to run a separate dbus session bus for rhythmbox, sharing the bus address between users through some unspecified means. Other users could then control a shared-ish rhythmbox instance using dbus clients; if they needed access to the actual UI, they could cause the current instance to quit, then start their own attached to their display. This would be quite tricky to set up, and wouldn't work as well as running a shared rhythmbox in vnc. _______________________________________________ rhythmbox-devel mailing list [email protected] http://mail.gnome.org/mailman/listinfo/rhythmbox-devel
