5 Replies Latest reply on Jul 15, 2009 1:57 PM by jbalunas

    global default queue

    asookazian
    asookazian Jul 14, 2009 6:47 PM

      5.5.3.1. Global default queue, defined in the web.xml file

      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 "significantly affect expected behavior" mean? What are some examples and/or negative consequences of using global default queue. I've used it in my RF/Seam app with no problems AFAIK. thx.



      • 1125 Views
      • Tags:
        • 1. Re: global default queue
          asookazian
          asookazian Jul 14, 2009 6:52 PM (in response to asookazian)

          How can we configure the global default queue (if possible) similar to this:

          <a4j:queue name="org.richfaces.global_queue" requestDelay="1000" />


          i.e. how can we add a requestDelay here, so that we don't need to add a4j:queue to each xhtml page: 
          <context-param>

 <param-name>org.richfaces.queue.global.enabled</param-name>

 <param-value>true</param-value>

</context-param>


            • Actions
          • 2. Re: global default queue
            ilya_shaikovsky
            ilya_shaikovsky Jul 15, 2009 6:05 AM (in response to asookazian)

            you could add queue definition to the upper template if using facelets.

              • Actions
            • 3. Re: global default queue
              jbalunas
              jbalunas Jul 15, 2009 1:54 PM (in response to asookazian)

               

              "asookazian" wrote:

              What exactly does "significantly affect expected behavior" mean?


              This is referring to the effect of the global default queue causing all Asynchronous JavaScript And XML requests becoming synchronous via the single global queue. That is what is meant here. If the global queue is turned on it can change the behavior on all views of the application without any visible or obvious setting.

              This should be explained in the docs.

                • Actions
              • 4. Re: global default queue
                asookazian
                asookazian Jul 15, 2009 1:56 PM (in response to asookazian)

                 

                "jbalunas@redhat.com" wrote:
                "asookazian" wrote:

                What exactly does "significantly affect expected behavior" mean?


                This is referring to the effect of the global default queue causing all Asynchronous JavaScript And XML requests becoming synchronous via the single global queue. That is what is meant here. If the global queue is turned on it can change the behavior on all views of the application without any visible or obvious setting.

                This should be explained in the docs.


                So does this mean we should try not to use the global default queue?

                  • Actions
                • 5. Re: global default queue
                  jbalunas
                  jbalunas Jul 15, 2009 1:57 PM (in response to asookazian)

                  https://jira.jboss.org/jira/browse/RF-7528

                    • Actions