oreilly sucks the kumara anyway because you end up with a file??
the deal is that you (really) have (really) a mulitpart mime encoded request
possibly containing binary content. so if you are.. and i am.. requiring
anything useful like a binaryinputstream to the content.. your out of luck
because oriely actually writes a file to your webserver ( how completley
rude!!! )
i've seen people use perl regex to get the content but in the end i wrote a
state machine to pass the mime request.. the trick is anticipating the end
of line characters and the contents terminating boundary.. also a browser
sometimes makes up its own little cavets like "oh i'm ie running on an apple
system.. so i'll only send 1 \n instead of the standard two after the
boundary", wierd and annoying..
regex seems nice because it (can) kinda tokenize it [request] all for you
too.. sorry about bashing orielly but if your storing the content into zip
files as blobs in the database then orielly is not for you.. but i'm sure
its pretty good at something =)
regards,
warren.
-----Original Message-----
From: Cris J. Holdorph [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, 13 June 2001 1:11 PM
To: [EMAIL PROTECTED]
Subject: An opensource (apache style license) file upload servlet
I've been searching the net, high and low, for implementations of
RFC 1867, "Form-based File Upload in HTML" in a Java Servlet. Specifically
a servlet that will run in tomcat 3.2.x.
The common answer seems to be the O'Reilly classes talked about in
Jason Hunter's "Java Servlet Programming" book. However, the license
for all of the com.oreilly.servlet.* code available from www.servlets.com,
(http://www.servlets.com/cos/license.html)
"that every person on the development team for that project owns a copy of
the book" for commercial use. My company can not meet that guarantee.
So, as far as that goes, I guess the O'Reilly classes are not an option.
Is there another option that is more Open Source, apache license style,
for doing http file uploads, in Servlets? I can implement my own from the
spec, but I sure hate to reinvent the wheel. Especially so much of that
Mime stuff.
I look forward to any answers this tomcat-user list can provide.
---- Cris J H
ps. In case I haven't been clear. It must be *FREE*, with *SOURCE*, for
*COMMERCIAL* use. If we have to "pay" for it, I already have those answers.
