At 11:18 am -0700 25/6/02, Richard Gaskin wrote:
Hmmm... still stumped on how to proceed, I'm afraid.
I think I misunderstood the original problem.
Here's the relevant snippet from my script:
put ftp://; tUser : tPword @ tHost \
/ tDir / into tBaseDestUrl
put 0 into tCounter
Richard,
IMO, A cleaner (and safer) approach is to upload files to a web server using
AltSAFileUp Library which should be compatible with file posting to
webservers using form based file upload (RFC1867).
Depending on what type of server you wish to upload, you can do the same as
a browser
Dave Cragg wrote:
At 3:30 am -0700 25/6/02, Richard Gaskin wrote:
For running handlers that need to wait for the upload to complete,
you could insert something like this at appropriate points:
repeat until condition
wait for messages
end repeat
Just be sure the condition will
--On Tuesday, June 25, 2002 11:18:37 -0700 Richard Gaskin
[EMAIL PROTECTED] wrote:
Dave Cragg wrote:
At 3:30 am -0700 25/6/02, Richard Gaskin wrote:
For running handlers that need to wait for the upload to complete,
you could insert something like this at appropriate points:
repeat
Richard,
Not sure if this helps, but I took a peek into the libURL scripts...
It seems like you can get messages completely blocked by finding this:
repeat while laFTPStatus[laUrl[laNx[x]]] is empty
wait for messages
end repeat
Which appears several time in a ulFTPSend handler. Just
At 10:36 PM -0700 6/25/02, Richard Gaskin wrote:
Geoff Canyon wrote:
At 11:35 PM -0700 6/24/02, Richard Gaskin wrote:
I have a fairly complex setup in which I nee to avid race conditions, and
using put seems to allow processing of other messages while it's
connecting and uploading.
Could
Dave Cragg did a great job with the new libURL, but I need something that
doesn't seem to be supported:
How can I upload a file synchronously, such that all scripts stop until
either the file is uploaded successfully or an error is encountered?
I have a fairly complex setup in which I nee to
At 11:35 pm -0700 24/6/02, Richard Gaskin wrote:
How can I upload a file synchronously, such that all scripts stop until
either the file is uploaded successfully or an error is encountered?
I have a fairly complex setup in which I nee to avid race conditions, and
using put seems to allow
Dave Cragg wrote:
At 11:35 pm -0700 24/6/02, Richard Gaskin wrote:
How can I upload a file synchronously, such that all scripts stop until
either the file is uploaded successfully or an error is encountered?
I have a fairly complex setup in which I nee to avid race conditions, and
using
At 3:30 am -0700 25/6/02, Richard Gaskin wrote:
For running handlers that need to wait for the upload to complete,
you could insert something like this at appropriate points:
repeat until condition
wait for messages
end repeat
Just be sure the condition will eventually come true.
--On Monday, June 24, 2002 23:35:33 -0700 Richard Gaskin
[EMAIL PROTECTED] wrote:
Dave Cragg did a great job with the new libURL, but I need something that
doesn't seem to be supported:
How can I upload a file synchronously, such that all scripts stop until
either the file is uploaded
On 6/25/02 5:30 AM, Richard Gaskin wrote:
My understanding of wait for messages was the opposite, that it was
designed to allow asynchronous behavior. Is there a way to use it to suspend
script execution and event messages while waiting for an upload to complete?
Would this work:
repeat
12 matches
Mail list logo
