I just want to remark that it's a little eerie to have the author of a book on your desk send you email. Maybe Kant will write me back next about his transcendental arguments =) Anyway, back to the topic at hand. Regarding (a) I'm not crazy about the proliferation of temp directories, but I guess that would do the trick as a last resort. I'm not quite sure I understand how to go about doing what you suggest in (b). Wouldn't I still need to be writing the file out somewhere, perhaps before I've discerned the other parameters I need to determine where I want to save to, and so I'm right back to (a)? Do other file upload implementations that don't require a directory at the get-go just try to store the uploaded file in memory till you're ready to specify a place to save to? (I'm thinking of jspsmartupload in particular). Does attempting to modify MultipartRequest so that it wouldn't require a directory parameter in the constructor sound totally futile? Thanks, Eddie >You can >(a) create a different temp directory for each request, or >(b) use the com.oreilly.servlet.MultipartParser to walk the request >piece by piece. The problem with piece-by-piece is there's no guarantee >the param(s) you want will come before the file(s). > >-jh- _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp ___________________________________________________________________________ To unsubscribe, send email to [EMAIL PROTECTED] and include in the body of the message "signoff SERVLET-INTEREST". Archives: http://archives.java.sun.com/archives/servlet-interest.html Resources: http://java.sun.com/products/servlet/external-resources.html LISTSERV Help: http://www.lsoft.com/manuals/user/user.html
