On Thursday 06 February 2003 11:19 am, Mike Noyes wrote: > Lynn, > Maybe (probably) I'm confused, but I thought one of the main advantages > of Chad's suggestion was it avoided the use of a single file database.
Mike, your not confused at all. I'm a bit confused to how nothing but a directory structure containing nothing but a 'value' is going to be parsed/sourced with onboard LEAF tools for use in conf files w/o templates. Further, how is Joe User going to locate something by hand if he needs to. I see a single file (not the real db) as being very useful as a translation layer between user/application and the db. I still have a couple of today's replies left to read, hopefully my confusion gets cleared up. I'm definately not the stongest coder on the block, so I may be simply missing the actual code implementation that is being suggested as well. The addition of Perl (that won't fit on a floppy) would make the entire suggestion appear in a different light personally. In the scope of things, I'm fishing for the best idea and would be relived to see a clear choice/implementation explained. It may well be there already, and I hope to find I'm just not grasping how it can work with our toolset. -- ~Lynn Avants Linux Embedded Firewall Project developer http://leaf.sourceforge.net ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ leaf-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/leaf-devel
