Preface the update with a rename. If the rename fails,
someone else is updating the file, if it succeeds update
the file and rename back when finished.
Suggestion: ftp is not the best way to handle such a task.
Use a database, XMLRPC or sockets is probably a better
way.
-Larry Bates
[EMAIL
Mike Meyer wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
here's a simple-minded suggestion: have the first client create a text
file on the remote server, and delete it when it is finished updating.
The second client can check for existence of this file before trying to
update.
Fuzzyman [EMAIL PROTECTED] writes:
Mike Meyer wrote:
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
here's a simple-minded suggestion: have the first client create a text
file on the remote server, and delete it when it is finished updating.
The second client can check for existence of this
hi all
am updating the same file in ftp, through multiple clients, but am
scared that two clients may open the same file at a time, and try
updating, then the data updated by one data will be lost.
So i have to provide some lock mechanism to that file in ftp, so how
can i lock it, if one client
here's a simple-minded suggestion: have the first client create a text
file on the remote server, and delete it when it is finished updating.
The second client can check for existence of this file before trying to
update.
cheers,
S
--
http://mail.python.org/mailman/listinfo/python-list
[EMAIL PROTECTED] [EMAIL PROTECTED] writes:
here's a simple-minded suggestion: have the first client create a text
file on the remote server, and delete it when it is finished updating.
The second client can check for existence of this file before trying to
update.
That's an old hack, dating
why, that's the nicest thing anyone's said about me today - and
probably true, since I started coding on punch-cards...
s
--
http://mail.python.org/mailman/listinfo/python-list
