Subject: Re: [linux-audio-dev] saving plugin settings
From: Kevin Conder (kconder_AT_interaccess.com)
Date: Sun Sep 16 2001 - 19:42:13 EEST
On Sat, 15 Sep 2001, Taybin Rutkin wrote:
> On Sat, 15 Sep 2001, Paul Davis wrote:
>
> > >of a burden if the state of each app in a complex environment had to be
> > >saved and restored individually.
> >
> > 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.
>
> One idea I had for this was for each application to define its own XML
> tag. Say <ardour-settings></ardour-settings>. Then, each application is
> sent the entire session file. The application would parse looking for its
> tag and would only read that part. This is trivial with an XML library.
I use SGML/XML for documentation. But I'm not entirely convinced
that XML is appropriate for config files.
My experience has been that existing XML parsers blow up when they
have to deal with large files (like a 700 page users manual). I'm worried
about what would happen if they had to parse a large config file similar
in size to a sendmail.cf.
What happens if the bottom of a large config file gets chopped
off? Will existing XML parsers still parse an invalid XML file? What if
someone manually edits a file and makes it invalid?
-- kevin at kevindumpscore dot com
This archive was generated by hypermail 2b28 : Sun Sep 16 2001 - 19:41:47 EEST