On Fri, Mar 18, 2011 at 6:01 PM, Johan Compagner <[email protected]> wrote: > besides that we must make sure that the object hiearchy and so on is not > suddenly in a wrong state.
That is the idea: the object hierarchy should not be put into the page store—essentially throwing away any changes made during that partially processed request. > And there are cases that request 1 is still way more important then request 2 > and request 2 may never just kill 1. (Request 2 is just a background polling > thread of are there any changes) Request 2 will only complete when request 1 is finished, so much for polling :). In most if not all cases where request1 takes longer than 10 seconds, it should be done in a background thread. Unfortunately JEE does not provide a good way to facilitate that. A bigger issue is that when request 1 has finished processing the listener phase, but rendering the response takes too long. What should happen in that instance? Martijn
