-
1. Re: ajax queues: Why not always on?
luxspes Aug 20, 2009 5:57 PM (in response to luxspes)In the docs says that:
"The global default queue is disabled by default, because artificial serializing of all Ajax requests on a page can significantly affect expected behavior. "
What exactly does that mean? (because to me, it seems like having an automatically enabled global queue always would solve all this overcomplexity problem) -
2. Re: ajax queues: Why not always on?
luxspes Aug 24, 2009 10:59 AM (in response to luxspes)And so RF-7755 is created.
-
3. Re: ajax queues: Why not always on?
ilya_shaikovsky Aug 25, 2009 7:01 AM (in response to luxspes)actually just set the web.xml param to turn it on for all the application.
-
4. Re: ajax queues: Why not always on?
jbalunas Aug 25, 2009 9:25 AM (in response to luxspes)Hi Luxspes, we have have been really busy working RF 3.3.2.CR1 and RF 4.0 ALPHA1 so we have not been able to get back to you.
The reason queues are not "on" all the time is that it would take the "Asynchronous" out of AJAX. All of a sudden all ajax requests would be serialized/synchronous instead of firing when called and returning as jobs finish on the server.
In some situations with Seam (JSF in general really) asynchronous requests can cause problems if requests are received out of order or while other requests are processing.
As Ilya said it is easy to turn the on automatically and on every view following the instructions for the web.xml param.
Hope this helps. -
5. Re: ajax queues: Why not always on?
luxspes Aug 25, 2009 11:29 AM (in response to luxspes)"jbalunas@redhat.com" wrote:
Hi Luxspes, we have have been really busy working RF 3.3.2.CR1 and RF 4.0 ALPHA1 so we have not been able to get back to you.
I cant wait to download RF 3.3.2.GA! (and of couse RF 4.0 when it is ready)
The reason queues are not "on" all the time is that it would take the "Asynchronous" out of AJAX. All of a sudden all ajax requests would be serialized/synchronous instead of firing when called and returning as jobs finish on the server.
Is that accurate?,because if it actually changed AJAX in to SJAX it would block the browser (and AFAIK it does not do that).
In some situations with Seam (JSF in general really) asynchronous requests can cause problems if requests are received out of order or while other requests are processing.
It really really would be great if you could give me a concrete example of something "weird" that could happen by using the global queue
As Ilya said it is easy to turn the on automatically and on every view following the instructions for the web.xml param.
Hope this helps.
Yes, it does (but a concrete example would be better). -
6. Re: ajax queues: Why not always on?
ilya_shaikovsky Aug 25, 2009 11:43 AM (in response to luxspes)Is that accurate?,because if it actually changed AJAX in to SJAX it would block the browser (and AFAIK it does not do that).
RichFaces queue highly customizable and has features of combining similar requests, aborting out-of-date page responce, dropping older ones if queue size exceeded and so on, so actually it will not block the browser. But it's enablement will really make all the events wait for another.It really really would be great if you could give me a concrete example of something "weird" that could happen by using the global queue
Jay talked in his comment not about requests that using global queue but about ones which not using ;)