thanks, we can workaround it for now > -----Original Message----- > From: Geoff Howard [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 20, 2003 12:08 PM > To: [EMAIL PROTECTED] > Subject: Re: action before upload handled? > > > Tim Olson wrote: > > >>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 > > > > > Ok. Well, this sort of delayed handling is planned, but is not even > started yet. The proposal on the table was to add a new > sitemap command > like map:adapt-request which would at that point allow > special handling > of "extra" request information. The idea is to facilitate > finer-grained > control over uploads, webdav, etc. > > Now, if you'd like to dive in and help develop that I'm sure > you'd get > some support with us over on dev (this was Stefano's brain > child). But, > if you just need to get something working right away, I'd > suggest taking > a client-side approach. Off the top of my head, I'd say > you'll have to > perform some action prior to the submit - like during an onsubmit() > handler. Since you need to signal the back end, you're > options will be > things like: script back to a function in the applet, load a > "special" > image or iframe/layer with an href handled by Cocoon which > will fire off > an action/flow script on request of that url. The last two > are pretty > hacky but should work just fine. > > HTH, > Geoff > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] >
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
