I agree that this case might be a one off; yet, the method he is using
he has used before, and might likely use again.
There is a better way; yet, it is still up to the client to enforce the
behaviours(insecure).
Input file(read/write enabled):
Can be written by any client; yet, they all have to agree to check
for a time delay marker, and to see if it has elapsed. If not elapsed
they cannot write; yet, this would also mean that the client has to know
the approximate time it would take to be able to write to the file on
the network, before setting the delay; otherwise, the write time window
might close and the client would overwrite the input file; yet, this
could possibly be caught by a second check by the client to see if the
write window was still open. If the window has closed it would have to
indicate that it wants to write again. A main thread handling client
acting like a message switcher would have to poll the file constantly.
There would also need to be a way of showing that the file is ready for
writing by other clients, because the switching client has copied all
the info that could be anything from a request to a whole file.
output file(read only):
All clients have access and they would all have to poll it continuously
This causes a very slow info passing system; yet, possibly more
reliable. You could have multiple files per connection to make it work
faster.
Juan Pablo Califano wrote:
As far as I know, SQLite uses the OS file locking facilities (which do seem
to be problematic in Macs). Anyway, I'm not saying this is the most robust
possible solution. I'm just saying that given the circumstances, it could be
good enough.
Cheers
Juan Pablo Califano
2009/1/10, Anthony Pace <[email protected]>:
Well the db is a raw file; thus, I was referring to the db.
If you look at my last few lines, I was trying to tell him how his system,
in which the file can be written to by all clients, can only work even
marginally well with a timed write delay; yet, nowhere did I say it was more
secure. In fact, if you look at my first line, I note that it is a bad way
to do things, and is very insecure.
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
_______________________________________________
Flashcoders mailing list
[email protected]
http://chattyfig.figleaf.com/mailman/listinfo/flashcoders
