Re: [LAD] Summercode 2008: LASH, pt. 3

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]
To: <linux-audio-dev@...>
Date: Wednesday, February 6, 2008 - 1:28 pm

Fons Adriaensen wrote:

Sure, and while we're talking about the LASH<->client protocol I still
don't see this being a problem. Any session that includes clients which
reside on multiple hosts will still require a local lashd running on
each host (even Bob agrees with this, which I didn't realize until
before we talked about it on #lad). The protocol that lashd uses to
communicate with its clients should IMHO be local.

In practice, the clients would still simply link against liblash and use
its API regardless of what liblash does internally. The internal
protocol could be anything, as long as it's not a Swiss army knife that
tries to do everything imaginable by itself.

When looking at how a multi-host session would work in practice, it's
obvious that what happens between the LASH daemons is key. This
communication has, in my opinion, more in common with the current server
interface than the client interface.

Consider this (monospace font required):

host host host
B A C
| | |
| LASH control app |
| | |
-------------- --------------- --------------
|server iface|<=========|server iface |========>|server iface|
-------------- --------------- --------------
|*LASH slave*| |*LASH master*| |*LASH slave*|
-------------- --------------- --------------
|client iface| |client iface | |client iface|
-------------- --------------- --------------
| | |
client 3 client 1 client 5
client 4 client 2 client 6

Here the "master" host's LASH is controlled by a user interface
application, and the "slave" hosts' LASHes are controlled by the master
LASH, and both use the same protocol. The control interface is built so
that it can tune in to both local and remote control messages. It may
well be based on OSC. The client interface protocol has no network
connectivity requirement.

The type of commands that a LASH server might receive from an UI -- load
project, save project, etc. -- are identical to those that it might
receive if it were a slave listening to a network socket. (I wonder, for
the second time today already, if this isn't what Bob had imagined as
well. There have been some misunderstandings at least on my part during
the discussion.)

One more thing about the LASH client and server interfaces. Dave
Robillard has expressed his opinion that the current situation where a
liblash client can register as either client or controller is tricky.
Patchage can't register as a LASH client and store some session-related
settings because it also needs to register as a LASH controller. This
calls for a fix, one solution being to completely separate/abstract away
the LASH server interface from the current API.

>>> For anything like lash to be useful here it would need to support

Very interesting thoughts. I'm afraid, though, that my circuit's too
loaded with LASH protocol stuff right now for me to figure out how to
fit your ideas into the domain of session management. :)

Juuso
_______________________________________________
Linux-audio-dev mailing list
Linux-audio-dev@lists.linuxaudio.org
http://lists.linuxaudio.org/mailman/listinfo/linux-audio-dev

Previous message: [thread] [date] [author]
Next message: [thread] [date] [author]

Messages in current thread:
[LAD] Summercode 2008: LASH, pt. 3, Juuso Alasuutari, (Sat Feb 2, 6:22 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Fons Adriaensen, (Mon Feb 4, 12:37 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Juuso Alasuutari, (Mon Feb 4, 4:19 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Fons Adriaensen, (Tue Feb 5, 11:31 am)
Re: [LAD] Summercode 2008: LASH, pt. 3, Juuso Alasuutari, (Wed Feb 6, 1:28 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Bob Ham, (Sat Feb 9, 6:26 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, St├ęphane Letz, (Tue Feb 5, 2:36 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Paul Davis, (Tue Feb 5, 2:39 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Fons Adriaensen, (Tue Feb 5, 3:31 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Bob Ham, (Mon Feb 4, 9:37 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Juuso Alasuutari, (Wed Feb 6, 11:31 am)
Re: [LAD] Summercode 2008: LASH, pt. 3, Bob Ham, (Wed Feb 6, 1:51 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Arnold Krille, (Tue Feb 5, 8:32 am)
Re: [LAD] Summercode 2008: LASH, pt. 3, Bob Ham, (Tue Feb 5, 4:04 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Bob Ham, (Tue Feb 5, 3:56 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Marc-Olivier Barre, (Tue Feb 5, 6:46 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Juuso Alasuutari, (Wed Feb 6, 11:32 am)
Re: [LAD] Summercode 2008: LASH, pt. 3, Nedko Arnaudov, (Mon Feb 4, 3:17 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Bob Ham, (Sat Feb 2, 7:06 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Juuso Alasuutari, (Sun Feb 3, 8:15 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Julien Claassen, (Sat Feb 2, 6:41 pm)
Re: [LAD] Summercode 2008: LASH, pt. 3, Nedko Arnaudov, (Sat Feb 2, 9:38 pm)