i solved this problem with poem access on my site by
creating new read and write functions that "lock" the
file while it's being read from or written to.
the lock is just a temporary file that is removed as
soon as the read or write is finished. the lock exists
only as long as it takes to grab the data out of the
file or write to the file ... so the lock does not
exists the whole time the script is running, just for
about a fraction of a second, if that.
read locks are time stamped so there may be multiples
of them, this is because a read lock only prevents
writing, not reading. a write lock is just a single
file that prevents other processes from writing to or
reading from the file.
the read and write functions recheck for the lock
file's existence about every 100th of a second. the
read function only checks for a write lock while the
write function checks for a read or write lock.
i'd share the functions with you, but i wrote them
in perl. should be very easy to do in rebol.
cheerfulness,
-----EAT
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.
