[LAD] Summercode 2008: LASH as a D-Bus service

Bob Ham rah at bash.sh
Tue Jan 22 22:22:22 UTC 2008


On Tue, 2008-01-22 at 21:32 +0200, Nedko Arnaudov wrote:
> Bob Ham <rah at bash.sh> writes:
> 
> >>  * lash does not preserve X11 related properties of apps, like on what
> >>    screen (dual-head) they were.
> >
> > Nor should it.  The X11 system is nothing whatsoever to do with LASH,
> > intentionally.  From LASH's perspective, anything to do with X11 is
> > entirely the client's responsibility.  Adding X11-specific functionality
> > into the protocol, the server and the library should not happen.
> >
> > Providing convenience functions to clients is a solution, eg
> > lash_x11_get_state_configs() and that returns a set of LASH configs
> > containing the state of the X11 system.  And, of course, functions to
> > restore the state.  But it should be separate from LASH itself, eg, in
> > some liblash-x11.
> >
> >>  * Supporting connections for things other than JACK (read ALSA seq)
> >
> > LASH already does support ALSA seq.  Future support would be connecting
> > via netjack, or firewire, or $next_big_thing.
> 
> Oh, sure, LASH should support network multimachine sessions but it has
> nothing to do with X11? I find this funny :)

Why do you find it funny?

> You want to use firewire for what exactly?

Taking audio from JACK client A on host 1 to JACK client B on host 2.

Bob

-- 
Bob Ham <rah at bash.sh>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://lists.linuxaudio.org/pipermail/linux-audio-dev/attachments/20080122/0c19cffd/attachment.pgp>


More information about the Linux-audio-dev mailing list