>   another solution, one that bo told me about, is to write
> a serialization server. then send all the data to the server
> script and let it handle writing/reading to/from the one
> data file on it's own.
        [I didn't already consider this one. It seem to be an usefull one in
my case.
        I will launch some tests ASAP.

        Thanks !

        Best Regards,

        chr== ]  

> Andrew Martin wrote:
> > 
> > > I'm confronted with a little but important problem...
> > >
> > > I'm using a block structure for storing data on a server. 40 PC's
> -soon
> > 80- could potentialy dump their data on the same time into one single
> data
> > file on the server.
> > 
> > Perhaps better would be for the 40 (or 80) PCs to each write their own
> data
> > into a file on a shared folder on their Hard Disk Drive. That way the
> PCs
> > don't have to _compete_ for network access at the same time. Then a
> program
> > on the server can periodically read each PC (say, every ten seconds or
> when
> > convenient) and accumulate the data files, one at a time.
> > 
> > Andrew Martin
> > Asbestos-suited Rebol...
> > ICQ: 26227169 http://members.nbci.com/AndrewMartin/
> > -><-
> > 
> > --
> > To unsubscribe from this list, please send an email to
> > [EMAIL PROTECTED] with "unsubscribe" in the
> > subject, without the quotes.
> -- 
> To unsubscribe from this list, please send an email to
> [EMAIL PROTECTED] with "unsubscribe" in the 
> subject, without the quotes.
-- 
To unsubscribe from this list, please send an email to
[EMAIL PROTECTED] with "unsubscribe" in the 
subject, without the quotes.

Reply via email to