3 Apr
2010
3 Apr
'10
7:17 a.m.
On Fri, Apr 02, 2010 at 09:32:15AM +0200, Nick Copeland wrote:
i dont understand this sentence.
an app like fst needs to be started with the correct plugin, to load a
config file for that plugin.
an app that only has state consisting of commandline options doesnt even
have save/load code. still can be supported by the corrent
implementation, it just needs to remember the options it was started
with.
--
torben Hohn
but basically its not so easy to implement
everywhere (some apps would
need to kill their jackclient which isnt possible.)
but i dont really see the big problem in killing an app and restarting
it right away.
most of the mapped memory will still sit in caches, and this will happen
pretty fast.
additionally it needs quite a lot of logic in the sessionmanager.
Yeah, it might have to maintain change logs to be able to remove bit of
config, it is a nice feature though: how would the session manager handle this ?
it cant know what the correct options are to reload the app with a
session file.
If you have a reload feature you don't need to know - you start all the apps and
then send the a reload request for a known file which you asked them to
save previously.