Subject: Re: [linux-audio-dev] saving plugin settings
From: Tom (stillone_AT_snowcrest.net)
Date: Sun Sep 16 2001 - 07:53:38 EEST
> theoretically, this is not hard to do. there is already a duplex
> connection between the LAAGA server and each client, and the server
> can just ask for XML to be delivered representing the state.
>
> of course, the devil is in the details. how to identify each client
> when restoring state, etc. that starts to requires the server to know
> much more about clients that i tend to feel is a good idea.
The method that I have in mind doesn't require any client data to be sent
to the server. Each client creates its own session file just like a
stand-alone app would, using the standard "save", "save as", and "save a
copy" commands. The only difference is that the save commands are issued
from the server instead of the user. The user enters the session name and
selects the type of save from within the server. The server creates its
own session file, which consists of just the session name and a list of all
currently active clients. Then the server issues a save command to each
client on the list. Each client creates its own session file with the same
name as the server's session file.
For restoring state, the user opens the desired server session file. This
causes the server to launch each client on its session list and command
each client to open its session of the same name. Again this is the same
behavior as with a stand-alone app, except that the "open" command is
issued from the server instead of the user.
Tom
This archive was generated by hypermail 2b28 : Sun Sep 16 2001 - 07:47:32 EEST