On Tue, Mar 23, 2010 at 8:18 AM, Mark Struberg <struberg@yahoo.de> wrote:

Hi!

The spec currently says:

"The container ensures that a long-running conversation may be associated with at most one request at a time, by blocking
or rejecting concurrent requests."

We do so, but now I get a pretty ugly BusyConversationException in an AJAX enabled JSF-2 component (Primefaces DataTable).

This may easily happen in other cases too and it would be really good to allow parallel requests to a @ConversationScoped bean!

Since this will get pretty heavy used in JSF-2 with <f:ajax/> we should imo aim to address this problem somehow.

Comet and other AJAX-push technologies may also get unusable this way, since they always have an open socket for this.

Also consider a page with 2 lazy loaded DataTables. They usually get rendered empty and will start to fill itself in parallel when the page gets rendered.

txs and LieGrue,
strub

PS: a similar issue with parallel AJAX requests has already been reported to the JSF EG for the ViewMap...

__________________________________________________
Do You Yahoo!?
Sie sind Spam leid? Yahoo! Mail verfügt über einen herausragenden Schutz gegen Massenmails.
http://mail.yahoo.com

_______________________________________________
weld-dev mailing list
weld-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-dev