> It's impossible to run code before the request reads in the file, > because Cocoon does this for you while it sets up the Request > environment object which must be finished before starting pipeline > assembly and processing. > > Ok, technically possible if > 1) you use a servlet filter or chain before Cocoon servlet. > or > 2) you subclass the Multipart handler (and possibly CocoonServlet and > Cocoon, etc.) to account for a delayed processing of the > multipart data. > > Now, I don't quite understand why this other server needs to > know what's > happening before this server acts. Can you explain that > more? Are you > working with gigantic files or something? > > Geoff
yes, users are uploading large images while using a java applet which connects to a backend rendering engine. an html page pops up for the upload form, then when the request starts, we notify the render engine that an upload is happening, which sends an alert to the java applet "please wait while...". when the upload completes, we notify the render engine of the file location, then it crunches the image in various ways, places it in the document, and finally unlocks the java applet with the new uploaded image in place --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
