[snip]
I really like the idea of the client pulling over the database (whatever
form) and accessing it directly. It offers a lot of flexibility.
I also really like the idea of leveraging the SIS db which is already in
use.
Finally, I really like Gary's examples of a shell script that can
retrieve data from a properly formatted text file.
Therefore:
* What if we were to include perl in the boel_binaries.tar.gz?
* 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)?
1. A booting client would retrieve the child db (and the master
db), and use a shell script to get it's info on where to find
it's boel_binaries tarball.
2. Once it had perl from the boel_binaries tarball, it could
then access the master SIS db directly.
-Brian
--
---------------------------------------------------
Brian Elliott Finley http://baldguysoftware.com/
phone: 630.803.8183 http://systemimager.org/
---------------------------------------------------
-------------------------------------------------------
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
