--- Peter Crowther <[EMAIL PROTECTED]> wrote: > > From: Jeng Yu [mailto:[EMAIL PROTECTED] > > The servlet (in Appserver A) then processes part > of > > the > > form input in the doGet method and then needs to > send > > the rest of the form to another web server > > (Appserver B) to process and return the results > > (response code or something) to the calling > servlet > > which is waiting for it. The servlet receives the > > results and based on the results, sends > > response back to the client, all within the same > doGet > > method. > > > > Is this doable, and What's the best way to go > about > > it? > > "Best" or "Easiest to code"? :-) > > "Best" from a performance point of view is to change > your application so that it's *not* all happening in > the same doGet call. You don't know how long your > call will take. You should submit the request via > some appropriate mechanism and return a holding page > to the user. Every so often, the holding page > should poll to see whether the call has completed. > You'll need some way of storing the results from > appserver B, along with a way of managing timeouts > and similar. Since you've not said how appserver B > expects its data, we can't really suggest specific > technologies. This approach minimises the number of > threads that will be waiting at any time.
Sorry, I should have mentioned how appserver B expects its data. Essentially, it expects its data via a URL call - post or get. In other words, appserver B is another web server elsewhere. So what options or specific technologies do you have in mind? Thanks, Jeng Send instant messages to your online friends http://uk.messenger.yahoo.com --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
