> I think you misread me. I meant that it could be loaded into memory
> along with the application. The application could index it
> internally (if necessary). The idea here is that it would only be
> read on the first use, or whenever there was a change in the source
> text file, but the application would not continually reference the
> text file.
> Doesn't that make sense?
It does, but I just am opposed to data replication and CPU being used
for such functions when there are known standards for directory access
that are far more efficient. If indexed, sure, great, but that's still
hitting the source file on every message to check for changes, and CPU
stress every time there are changes.
It's not that it can't be done--it already is done all over--but I
have a predilection for existing, replicable, scaleable query
languages like SQL, LDAP, even xBase (and their respective stable back
ends) when dealing with appications which require up to hundreds of
thousands of values to be stored. It's the sort of thing that seems
easy until you watch it grow--and crumble under load.
--Sandy
------------------------------------
Sanford Whiteman, Chief Technologist
Broadleaf Systems, a division of
Cypress Integrated Systems, Inc.
e-mail: [EMAIL PROTECTED]
SpamAssassin plugs into Declude!
http://www.mailmage.com/download/software/freeutils/SPAMC32/Release/
---
[This E-mail was scanned for viruses by Declude Virus (http://www.declude.com)]
---
This E-mail came from the Declude.JunkMail mailing list. To
unsubscribe, just send an E-mail to [EMAIL PROTECTED], and
type "unsubscribe Declude.JunkMail". The archives can be found
at http://www.mail-archive.com.
