how is pulseaudio supposed to work?

[Richi Plana]

On Sun, 2007-12-16 at 12:30 -0600, Callum Lerwick wrote:
> > I believe
> > it's the session manager, which makes sense because the session manager
> > is a part of a bigger app (the DE) that knows it will actually use the
> > sound server.
> 
> No no no. The Pulseaudio library should take care of starting the damn
> daemon. Like esd did.

Just for clarification's sake: I'm not saying I support the session
manager starting the sound server daemon ... just that that's how I
believe it's currently implemented.

Using the library was one of the approaches I mentioned and seems to be
the least work-intensive to implement, though doing service starting
with associated well-known server ports a'la xinetd is generic enough
that if everybody started doing it, we may actually appease all those
users who keep clamoring for no-switching on of unneeded services which
are currently done by default. (I know I've had to switch of some
services like isdn, hplip, bluetooth, hidd, lm_sensors, etc.)
--

Richi Plana