But the only thing we can reall support it is through 2 ways:
1> use shared resources 2> we drop the session lock and the developer uses a different pagemap for the long request. johan On 2/14/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 2/14/07, Johan Compagner <[EMAIL PROTECTED]> wrote: > No it doesn't yet generate stateless urls yet. > See (for starters) > > public final CharSequence urlFor(final Component component, > final RequestListenerInterface listener) > > and > > public final CharSequence urlFor(final Component component, > final IBehavior behaviour, final RequestListenerInterface > listener) Ok. Can we put it on the list/ open a JIRA issue for it? > Long user request should really be avoided. Because every default > installation of > one of the webcontainers will break then. > i think resin/tomcat/jett? all default to a thread pool of 100? > So if you have a more then 100 sessions then more and more uses long running > things But that's ultimately for the container and user to decide. We (from the framework) can recommend stuff but we should be careful not to make too many presumptions. Also, the alternative, doing it in a separate thread, may not always be possible for people. It's still officially discouraged to work with threads in J(2)EE applications (though I never agreed with it) and just may have it's own issues. Eelco
