* Dossy Shiobara <[EMAIL PROTECTED]> [20051228 15:55]: > What's the use case you're looking to implement? If it's small file > uploads, it's probably just simpler to "fake it" using an animated > spinwait image.
Uploads of preproduced sound files for a radio station, from appx. 50-100MB size each. Depending on the connection of the user this can take up to a few hours in our experience. Being able to display the progress and some kind of ETA would be essential for that. With that kind of progress bar it would actually be quite userfriendly, especially because the upload can be integrated with the web application and doesn't need any external software (and extra authentication) on the client like ftp. > If you're handling large file uploads and need somewhat accurate display > of progress, then yes, a change to the core will need to be made to > expose the bytes received in one conn thread to another conn thread. If > security isn't a big concern (how bad is it if a user is able to find > out the progress of another user's upload?) then implementing this > change isn't necessarily a /lot/ of hacking around. > > What would be the best way of exposing this as a Tcl command, though? > I'm thinking "ns_info conn $threadId" which returns a Tcl list of > information about a conn. But how to find out from another thread the $threadId of the desired uploading connection? If "ns_info conn $threadId" contains the URL than this would be possible, by putting some identifier of the user session into the URL of the upload form. Essential would also be the availability of the Content-Length header content in a "ns_info conn $threadId". 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.
