Anyone noticing stalled uploading? find a solution?
Josh Mellicker
josh at dvcreators.net
Mon Nov 12 15:27:42 EST 2007
Thanks everyone for all your help.
I think found what was causing my problem, which was checking for the
same filename on the remote server before each upload.
Continually getting the remote list of files was stalling my uploads
(I think).
It seems to be fixed it by using "load" to cache the files in the
remote folder first, then accessing the cached list instead of
hitting the remote server multiple times:
put theFTPstring(tLineNum) into tFTPstring
if the uCachedURL of me is not tFTPstring then
load URL tFTPstring
set the uCachedURL of me to tFTPstring
end if
Here's the whole handler, suggestions and criticisms welcome!
if the hilite of btn "rename with unique name" then
-- check for same name file on remote server
put theFTPstring(tLineNum) into tFTPstring
if the uCachedURL of me is not tFTPstring then
load URL tFTPstring
set the uCachedURL of me to tFTPstring
reportStatus "just set the tFTPstring to" && tFTPstring --!
end if
put URL theFTPstring(tLineNum) into tList
repeat for each line tLine in tList
delete word 1 to 8 of tLine
put tLine & cr after tRemoteFileList
end repeat
delete char -1 of tRemoteFileList
put tRemoteFileList into tRemoteFileList2
filter tRemoteFileList with "*" & tFileName & "*"
if tRemoteFileList is not empty then
put stripExtension(tFileName) into tFileNameRoot
put theExtension(tFileName) into tExtension
repeat
add 1 to x
put tFileNameRoot & "-" & x & "." & tExtension into
tFileName
put tRemoteFileList2 into tRemoteFileList
filter tRemoteFileList with "*" & tFileName & "*"
if tRemoteFileList is empty then exit repeat
end repeat
end if
end if
On Nov 11, 2007, at 7:34 PM, Ken Ray wrote:
> On Fri, 9 Nov 2007 13:52:19 -0800, Josh Mellicker wrote:
>
>> I am uploading a list of files.
>>
>> After uploading a few files with no problem, uploading "stalls" with
>> no progress, and no timeout message is sent.
>
> Yes, I have run into the same thing with large files, where the
> incoming progress messages hit some point about 99% of the way through
> the upload (using "post", btw) and then constantly returning the same
> number of bytes uploaded. I found that if I let it run long enough to
> match the rest of the bytes (i.e. if it was uploading at 30K/sec
> and it
> stalled with 300K left on a 150MB file, I would let it wait for at
> least 10 seconds), and then terminated the upload, it would
> actually be
> at the destination fully uploaded.
>
> I thought it was just me, but I'm glad I'm not the only one. Now that
> Dave has suggested checking the result of the post for errors, I'll
> see
> if I can make that work. If not, I'll post my results.
>
>
> Ken Ray
> Sons of Thunder Software, Inc.
> Email: kray at sonsothunder.com
> Web Site: http://www.sonsothunder.com/
> _______________________________________________
> use-revolution mailing list
> use-revolution at lists.runrev.com
> Please visit this url to subscribe, unsubscribe and manage your
> subscription preferences:
> http://lists.runrev.com/mailman/listinfo/use-revolution
More information about the use-livecode
mailing list