I don't understand why you can't just make the ServletDispatcher figure out if the request is multipart and if so act accordingly? Why not make the entire thing transparent and also still avoid using filters unless absolutely necessary. I know most implementations can do filters now, so that's not the issue, but the more transparent this feature is, the better! Just my two cents...
-Pat ----- Original Message ----- From: "Matt Baldree" <[EMAIL PROTECTED]> To: "Webwork-User" <[EMAIL PROTECTED]> Sent: Saturday, May 18, 2002 11:51 AM Subject: [Webwork-user] multipart support > I added multipart support to WW. I looked at a couple of approaches at > solving this problem and settled in using a filter to wrap the request. I > thought this was the cleanest, less obtrusive solution. You have the ability > to choose between Jason's multipart parse (watch the license) and Pell's by > setting a new property setting "webwork.multipart.parser". You can always > add your own parser and adapter if you like. See "Multipart Request Test" > for more details. > > -Matt > > > > _______________________________________________________________ > Hundreds of nodes, one monster rendering program. > Now that's a super model! Visit http://clustering.foundries.sf.net/ > > _______________________________________________ > Webwork-user mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/webwork-user > _______________________________________________________________ Hundreds of nodes, one monster rendering program. Now that's a super model! Visit http://clustering.foundries.sf.net/ _______________________________________________ Webwork-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webwork-user
