On Fri, Jan 22, 2010 at 3:03 PM, Jeff Rogers <[email protected]> wrote: > The YUI upload control looks like a good place to start for the flash > client-upload feature. I haven't looked into it too deeply tho, so I don't > know what the server side looks like. > > YUI Uploader widget: http://developer.yahoo.com/yui/uploader/ > > Other that that, I was pondering the plain upload issue. Since > IE/Chrome/Safari are timing out on the upload, I wonder if the connection > could be kept alive by sending something - anything - back to the client > while it is still uploading.
This is just caused by a brain damaged application. TCP/IP handles connection timeouts all by itself. As long as packets are being sent and acknowledged received, the application should not care. But very likely what is happening is that you have a blocking worker thread with is being controlled by another thread just using a simple timeout, without monitoring progress. Anyone who has noticed their browser freeze while loading google analytics, or some other ad iframe has experienced this poor event programming model. Either Firefox avoids this with active monitoring, or it doesn't use a timeout at the application level, or the timeout is very large. > This might be doable with Jim's new "read" > filter. Of course, the browsers might respond to data by closing their > connection or stopping sending, or crashing (you never know with IE). And > then even if it works, you have the problem of not having the tcp connection > interrupted for however long it takes, which can be iffy in the world of > flaky wireless connections and ISPs. Until the entire POST is complete, you have no method of communicating back to the client, this is the ultimate cause of the no progress being reported. To stay within the HTTP protocol, you would have to send multiple smaller chunks, and wait for the server to acknowledge it has received the data at the application level. Also, the chunked transfer encoding doesn't really help here since proxies are sometimes required to remove this encoding, cache the entire body and maybe retransmit it in chunks. tom jackson -- AOLserver - http://www.aolserver.com/ To Remove yourself from this list, simply send an email to <[email protected]> with the body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of your email blank.
