[ardour-dev] hacky LASH'ifying ardour

[Florian Schmidt]

Hi,

i wonder whether it would make sense to have ardour simply store the
name of its own session file on the LASH server. This way, when
restoring a LASH-session, LASH would simply tell ardour the name of its
ardour-session file for the LASH-session and ardour would then simply
load that.

Ardour would also react to LASH requests for saving state by simply
saving its own ardour-session file.

When the user decides to load a different ardour-session, or save it
under a different name while a LASH session is open, ardour would send
the name of the new ardour-session file to the LASH server.

What do you think?

I know it's a hack, but it might work out alright in practice for many
usecases.

Regards,
 Flo

-- 
Palimm Palimm!
http://tapas.affenbande.org