Thanks for the reply. Sure - I can understand that if the client submits the form directly to the separate servlet, then this would achieve the "background processing thread" on the server side.
However, wouldn't this mean that the Wicket application loses control in that client browser window, since it has been passed over to the separate servlet? The only way I can see this setup working in the sense that a client to be able to continue working somewhere else (perhaps on a different page of the Wicket application) whilst uploading, would be to open a new browser window on the client and have that new window perform the submit to the separate servlet. Our Wicket application is stateful, but hopefully the opening on a new window wouldn't cause problems. So am I on the right track with the above or am I missing something here? Also, would it still be possible to use Wicket components with a submit form posting to the separate servlet? I'm just thinking if I wanted to use Wicket's single file upload (demonstrated here: http://wicketstuff.org/wicket/upload/single?0), whether that would still be possible. -- View this message in context: http://apache-wicket.1842946.n4.nabble.com/Asynchronous-File-Uploads-tp2541855p3077766.html Sent from the Users forum mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
