Web database suggestions
chipp at chipp.com
Tue Jan 25 11:37:26 CST 2005
Considering putting a single text file for each record on your server.
That way you won't have all the overhead of downloading the whole thing.
Do your business logic (search sort etc) in the client. Have a single
index file on the server with all the record .txt files.
Hope this makes sense.
Richard Miller wrote:
> I'm looking for a simple solution for storing and accessing data on a
> hosted server. Initially, the database need hold only about 1000
> records, containing simple contact information (15 fields). Reading and
> writing data is the main purpose... only a small amount of searching
> need take place. Access will be directly from a Rev application (not a
> browser or html file). Suggestions?
> I've been experimenting with placing a simple text file on the server
> and accessing it as if it was a local file, using lines like:
> put line 1 of url "ftp://myaddress.com/data.txt" into var1
> This seems to work reasonably well for testing purposes, but access time
> is rather slow (even through a broadband connection) and the file seems
> prone to corruption. Comments?
> Richard Miller
> Imprinter Technologies
> use-revolution mailing list
> use-revolution at lists.runrev.com
More information about the use-livecode