Subject: Re: [linux-audio-dev] App metadata intercomunication protocol..
From: Vincent Touquet (vincent.touquet_AT_pandora.be)
Date: Tue Jul 23 2002 - 12:31:39 EEST
On Tue, Jul 23, 2002 at 08:43:36AM +0200, n++k wrote:
>Why not use an SQL database for storing session/project metadata?
>(configuration and such) We have the benefit of having a few quite
>stable free software SQL databases. (mysql, postgresql, sapdb) so
>requiring one wouldn't be too much to ask.. The persistence protocol
>(sql) is already there and tested, the administration is as easy as
>with plain text files, and (I think) the schema is a lot easier to
>design than that of a set of interrelated XML files. (hierarchical
>databases?)
(cut)
Well you are entering the souvereign entity
of a program and asking them to change
the format they are very used to
and dump it into a database ?
To me that sounds like making
a big soup of a nice modular
system again.
Let the programs keep their
own settings in their own way,
just tell them when to save them.
Also: are you going to impose
people to install a RDB just
because they want their states
saved ?
Then comes the issue: which RDB,
you need choice, so you have to
provide a database abstraction layer.
Its not worth it in my eyes ...
regards
vini
This archive was generated by hypermail 2b28 : Tue Jul 23 2002 - 12:47:07 EEST