Check the size of the file, check it again in 2 seconds. If the size
is the same, the file should be on the server...
But your "flag-file" should do just as easy...
Warm regards,
Ton Kuypers
Digital Media Partners bvba
Tel. +32 (0)477 / 739 530
Fax +32 (0)14 / 71 03 04
http://www.dmp-int.com
On 18-mei-06, at 15:20, Richard Miller wrote:
I've got one stack sending a file out to server, and a separate
stack (on a separate machine) scanning the server for the
availability of that file. When it sees it, it needs to retrieve it
from the server.
Problem is, this second stack is seeing the availability of the
file BEFORE it has completely transferred onto the server. If it
starts retrieving it when it first sees it, well... the result
isn't good.
Is there any simple way for the second stack to know the file
transfer is complete before it starts accessing this file? I
realize I could have the first stack send a small "flag" file out
to the server after the original file was transferred, and the
second stack could wait until it sees that flag... but I'm
wondering if there isn't some easier way.
Thanks.
Richard Miller
Imprinter Technologies
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your
subscription preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
_______________________________________________
use-revolution mailing list
[email protected]
Please visit this url to subscribe, unsubscribe and manage your subscription
preferences:
http://lists.runrev.com/mailman/listinfo/use-revolution
