RichFaces
  1. RichFaces
  2. RF-3131

Implement properly requests queue for a AJAX submit.

    Details

    • Type: Feature Request Feature Request
    • Status: Closed (View Workflow)
    • Priority: Major Major
    • Resolution: Done
    • Affects Version/s: 3.2.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None
    • Similar Issues:
      Show 10 results 

      Description

      For a any cases sequence if ajax requests is important. Existing events queue must be extended to a queue events from different components and send new request only afer previsious is completed.
      Other possible option - merge parameters from a different events to a one request ( instead of replace ).
      All behaviors ( collect events from one components, queue events and merge ) must be configurable.

        Gliffy Diagrams

          Issue Links

            Activity

            Hide
            Sergey Kurenkov added a comment -

            It would be nice to have the default behavior of all ajax communications to go through one queue. Even though there might be a few cases where user want one request to execute independently of other, it seems that in 95% of the cases we'll want the request/responses to execute serially. This will help prevent all sorts of race-conditions that might happen.

            Additionally, the ability to specify in one place the default queue that all ajax requests go through will be useful. For example, perhaps in web.xml parameter like:

            <context-param>
            <param-name>org.ajax4jsf.DEFAULT_EVENT_QUEUE_ENABLED</param-name>
            <param-value>true</param-value>
            </context-param>

            This would tell a4j to send all ajax requests through one queue.

            Show
            Sergey Kurenkov added a comment - It would be nice to have the default behavior of all ajax communications to go through one queue. Even though there might be a few cases where user want one request to execute independently of other, it seems that in 95% of the cases we'll want the request/responses to execute serially. This will help prevent all sorts of race-conditions that might happen. Additionally, the ability to specify in one place the default queue that all ajax requests go through will be useful. For example, perhaps in web.xml parameter like: <context-param> <param-name>org.ajax4jsf.DEFAULT_EVENT_QUEUE_ENABLED</param-name> <param-value>true</param-value> </context-param> This would tell a4j to send all ajax requests through one queue.
            Hide
            Nick Belaevski added a comment -
            Show
            Nick Belaevski added a comment - Duplicates https://jira.jboss.org/jira/browse/RF-4387
            Hide
            Jay Balunas added a comment -

            Part of a bulk update, all resolutions changed to done, please review history to original resolution type

            Show
            Jay Balunas added a comment - Part of a bulk update, all resolutions changed to done, please review history to original resolution type

              People

              • Assignee:
                Nick Belaevski
                Reporter:
                Alexander Smirnov
              • Votes:
                7 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Development