[Dev] gui instance host question

[Henrik Frisk]

Stephen Sinclair <sinclair at music.mcgill.ca> wrote:

> On Tue, Jul 8, 2008 at 11:51 AM, Henrik Frisk <mail at henrikfrisk.com> wrote:
> > The library holds a local copy of the current 'piece' and saves it to
> > the db on user demand. However, the library could equally well work
> > against the server, though we do not have this implemented yet.
> 
> Except that the library is instantiated once in the GUI and once in
> the module host, so there are two "local copies".  

This is not the way it should be. The GUI should just reflect what is
loaded in the master (see below) instance host. But if two instances of
the instance host *are* instantiated (wow, that sounds like a joke :)),
which is legal, only one will load and save data: the one assigned
'master'. The others are slaves. But I may not understand what it is
your are asking...

> I know that these things aren't yet implemented, but just wondering if
> the plan is to perform this communication through the database or some
> other mechanism such as OSC.  Actually what I really wanted to know
> was whether the library would take care of the communication or
> whether the GUI is required to use OSC, and I think this question has
> been answered.
> 
> (If I understand correctly, it's "OSC for now, but eventually other APIs"..)
> 
This is most certainly right. And if I could choose I would like to get
started with the 'other API's' rather sooner than later, in particular
the RPC interface, but also a C API. For my own purposes I would like to
have a CLI to the library.

Sorry if I'm not understanding your questions.

best,

Henrik