* Tom Jackson <[EMAIL PROTECTED]> [20051229 08:07]: > There are problems on both the client and server side. Client browsers cannot > send binary data. AOLserver loads the entire request before a connection > thread is started. That means that there isn't any opportunity to save data > in chunks, just in case something goes wrong during the lengthy upload. > > One result of this is that, maybe, ns_conn will not have any data until all > the request is finished being read from the sock. So you can't get a progress > report from the server.
I was referring to this mail from Jim Davidson: http://article.gmane.org/gmane.comp.web.aolserver/12319/match=4+5+file+temp """ First 4.0 doesn't support this file overflow stuff which you probably don't need. It's in 4.5 and no parsing is done for you -- you just get a NULL form, access to the fd, and an NS_CONN_FILECONTENT flag bit and you're on your own. The reason is the parser is currently designed to scan the content in one memory block -- this would need to be changed (carefully). """ I don't fully understand it and don't know about aolserver 4.5 plans, but this sounds to me like it could mean that something that allows upload tracking is in preparation. Something that would allow me to redirect an incoming POST request to some other script based on the URL, even if all the decoding has to be done by the script itself, would be extremely helpful already. Everything that avoids the 'load all data beforehand' behaviour from aolserver. > At any rate, core hacking will be required to do progress or recovery on the > server, and would still require special application code. > > So here is what I looked at. A simple tcl shell script (loading libnsd.so) > that puts chunks of data to the AOLserver. Progress can be recorded and > reported on the client side. This only solves the progress report. [...] This sounds interesting. Although I'm not sure if in the case some client side software is required anyway I wouldn't just go back to a standard ftp or webdav client, which should be able to handle tracking upload progress, resumes, a common interface and binary transfers (not sure about webdav in that point). regards, Til -- 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.
