On Tue, Feb 11, 2003 at 10:34:41PM -0600, Brian Elliott Finley wrote: > Therefore: > > * What if we were to include perl in the boel_binaries.tar.gz?
perl is a beast - i'd like to avoid this if at all possible (shocking, huh?) keep in mind this is all running in a ramdisk on the client - perl binaries + libraries + the memory it takes up at runtime. i remember sean mentioning some embedded perl project(s) - what kind of overhead do they incur? what are they missing vs. a full perl distro? another concern is architecture portability of the perl interpreter we choose. based on doing backports of the debian perl package, i can say it will likely increase build times substantially, but this is a minor concern. > * What if the master database was based on the current SIS db, > and whenever it was updated, a small chunk of the data (just > enough to provide a client info on where to find the > appropriate boel_binaries.tar.gz) was written to a separate > file in a plain text db format (ala Gary's example)? another option is to make SIS use a plain text db format that can be parsed in shell. and another option is a mechanism by which the client could query the remote database, and get the information in a parseable form - this is what i'd prefer - leaving as much complexity on the server as possible. ------------------------------------------------------- This SF.NET email is sponsored by: SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See! http://www.vasoftware.com _______________________________________________ Sisuite-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/sisuite-devel
