Hi all --

does anyone care about HTTP upload with Quixote?  We have found it to be
unreliable with large uploads over slow links; at first we thought it
was due to buggy browsers, but then I sat down and implemented an
upload.cgi script that doesn't use the upload support in Python's cgi.py
at all (except for some MIME header-parsing code).  Turns out that it
works perfectly well -- in other words, I suspect that HTTP upload to
Quixote is flaky because Quixote ultimately relies on cgi.py.

My inclination is to rip all support for HTTP upload out of Quixote.
If my upload.cgi script works as well in real life as it does in
testing, I might sit down and figure out how to put HTTP upload support
back into Quixote, but I doubt it would be as transparent as it is now.
(I *think* the flakiness stems from over-generalization in cgi.py; the
upside of that over-generalization is that an HTTP request with an
uploaded file is treated much like any other HTTP request.)

Would anyone be greatly inconvenienced if I either removed HTTP upload
support, or replaced it with something that might be completely
different from the current interface?  (For example, code that handles
an upload might get a different type of request object.)

        Greg
--
Greg Ward - software developer                gward@mems-exchange.org
MEMS Exchange                            http://www.mems-exchange.org