Subject: Re: [linux-audio-dev] saving plugin settings
From: Paul Davis (pbd_AT_Op.Net)
Date: Sun Sep 16 2001 - 09:10:27 EEST
>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.
sounds good, except that its generally considered poor form on
unix-like systems for applications to know which executable file (as
in, a full pathname like /usr/local/bin/whatever) they are derived
from. this makes it hard to identify the clients unambiguously, and
its what i meant by:
>> 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.
in theory, each client could look at the zero-th argument passed to
it, but there is no guarantee that this will tell you the executable
file that it was "invoked" as. so its hard to know what the clients
were ...
--p
This archive was generated by hypermail 2b28 : Sun Sep 16 2001 - 09:11:06 EEST