I advocate the pluggable approach. That way if the admin wants to have mono sandboxed to 'ini' style flat files, then it's possible. I advocate flat files - it's not as if there will be huge amounts of data stored ... or will there be?
Suggestions ini files xml files berkley db ... other ----- Original Message ----- From: "Dietmar Maurer" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Cc: "Mono List" <[EMAIL PROTECTED]> Sent: Wednesday, September 18, 2002 5:39 PM Subject: Re: [Mono-list] Registry, text or binary? > On Wed, 2002-09-18 at 17:22, Everaldo Canuto wrote: > > Hello, > > > > I start a implementation of Registry Classes on Linux. > > For emulate a WinRegistry classes on Linux I think to save public data > > in the file /etc/system.reg and a private data on /home/user/.user.reg > > My problem is to decide which format to use to save data. > > Text file or binary file? If binary, What type of algoritimo to use? > > Simply make the backend pluggable ;-) It would be then possible for the > user/admin to select the backend. Both gconf and bonobo-conf uses such > pluggable approach. > > The nice thing is that we now have "interfaces" in C#, so its easy to > define/implement such plug-ins. > > - Dietmar > > > _______________________________________________ > Mono-list maillist - [EMAIL PROTECTED] > http://lists.ximian.com/mailman/listinfo/mono-list _______________________________________________ Mono-list maillist - [EMAIL PROTECTED] http://lists.ximian.com/mailman/listinfo/mono-list
