[
https://jira.jboss.org/jira/browse/RF-5788?page=com.atlassian.jira.plugin...
]
Nick Belaevski commented on RF-5788:
------------------------------------
Changes made:
1. Status now shows activity even after request has been aborted until request is
completed or terminated
2. Aborted (e.g. by ignoreDupResponses) requests now obey timeout
3. Queue ignores ignoreDupResponses when it's full (for the current implementation,
when size = 1)
Queue: ignoreDupResponse functionality change
---------------------------------------------
Key: RF-5788
URL:
https://jira.jboss.org/jira/browse/RF-5788
Project: RichFaces
Issue Type: Task
Affects Versions: 3.3.0
Reporter: Ilya Shaikovsky
Assignee: Nick Belaevski
Fix For: 3.3.1
Current state:
1) queue has ignoreDupResponces defined as true
2) request ?omes to queue and fired after its delay
3) new similar request comes to queue
4) previous one client side processing aborted - new one sent.
RESULT parallel requests occur.
To Be Changed:
4) new request should wait till previous response returned(but the response should not be
processed) and then to be sent.
RESULT just client-side response processing should be ignored but queue should works as
for normal requests (without ignoreResponse). New request waits till previous actually
finished.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira