Details
Description
The Push Server is not unblocking a pending blocking request when a new blocking request is received due to opening a new asynchronous ICEfaces application in a new tab within the same browser instance.
Activity
Ken Fyten
made changes -
Status | Resolved [ 5 ] | Closed [ 6 ] |
Assignee | Jack van Ooststroom [ jack.van.ooststroom ] |
Jack Van Ooststroom
made changes -
Status | In Progress [ 3 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Jack Van Ooststroom
made changes -
Salesforce Case | [] | |
Fix Version/s | 1.8 [ 10161 ] |
Jack Van Ooststroom
made changes -
Status | Open [ 1 ] | In Progress [ 3 ] |
Jack Van Ooststroom
made changes -
Field | Original Value | New Value |
---|---|---|
Assignee | Jack van Ooststroom [ jack.van.ooststroom ] |
Jack Van Ooststroom
created issue -
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #18710 | Tue Mar 31 15:59:48 MDT 2009 | jack.van.ooststroom | Fixed JIRA |
Files Changed | ||||
MODIFY
/icefaces/trunk/icefaces/push-server/src/org/icesoft/faces/push/server/RequestManager.java
|
The Push Server's logic was incorrect. Basically, the following happened:
1. There's an outstanding blocking receive-updated-views request to the Push Server for ICEfaces application 1 with ICEfaces ID 1.
2. A new tab is opened to ICEfaces application 2 with ICEfaces ID 2.
3. A new blocking receive-updated-views request to the Push Server is issued but now with ICEfaces IDs 1 and 2.
4. Due to incorrect logic the previous blocking receive-updated-views request with ICEfaces ID 1 is not unblocked.
When 3. occurs, any outstanding blocking receive-updated-views request with an ICEfaces ID contained in the new blocking receive-updated-views request should be unblocked.
The improved logic is in place. Marking this one as FIXED.