* Dossy Shiobara <[EMAIL PROTECTED]> [20051228 21:18]: > > Ouch. Have you considered making an upload applet? Together with a > > more advanced server side solution, you can then do things like > > resume if the connection craps out, while still using HTTP. > > I'm thinking the same thing: for real large files, you really want to > use an upload applet -- today, probably a simple Flash SWF. Something > that can do upload resumes might be crucial, especially for large files > over slow links, since as far as I know, plain HTTP doesn't support > byte-range file uploads.
I've seen this demo of a java upload applet for example: http://www.radinks.com/upload/applet.php - propably there are also open source versions similar to this out there somewhere or one could write ones own without too much effort, but I think it has some disadvantages, mainly: *) Need the user to grant filesystem access manually (try the demo). I can imagine how this will create some kind of irritation with the lesser experienced users. *) Uncommon interface. It's just not as familiar to the user as the file upload widget that produces a file selection dialog native of his or her own operating system. I want something that is working as seamless as this: http://sean.treadway.info/demo/upload/ You're right about the upload resume, that would remain an issue with normal http upload. I'd rather tend to offer an alternative route to those users who suffer from connection problems, e.g. via webdav of ftp, and have an easy ajax thingy like above. > Maybe it'd be cool to develop a very simple, skinnable and reusable file > upload Flash widget. I should see how much the Flash dev. stuff costs > -- it's about time I started getting into it. Don't know much about flash but I guess the same security issues with accessing the file system and unfamiliar file selector interface apply. Even if I could not convince you now why I prefer normal http upload, could someone make a guess wether it would be possible to implement the "ns_info conn $threadid" command in an aolserver module? Or is a core modification required? And coming back to the original question, does Aolserver 4.5 offer anything new in this regard? thanks, 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.
