[jira] [Commented] (WICKET-4723) tracking id retrieved in AtmosphereBehavior#onRequest() is always 0
[ https://issues.apache.org/jira/browse/WICKET-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442680#comment-13442680 ] Sean Lin commented on WICKET-4723: -- a related issue of atmosphere. https://github.com/Atmosphere/atmosphere/issues/544 tracking id retrieved in AtmosphereBehavior#onRequest() is always 0 --- Key: WICKET-4723 URL: https://issues.apache.org/jira/browse/WICKET-4723 Project: Wicket Issue Type: Bug Components: wicket-atmosphere Affects Versions: 6.0.0-beta3 Reporter: Sean Lin Assignee: Emond Papegaaij jquery.atmosphere.js will always use 0 as initial tracking-id to send request, and then reassign it from server response. AtmosphereBehavior#getUUID() shouldn't return the tracking-id from request header, since the initial request's tracking-id is 0. The correct way to retrieve tracking-id is calling AtmosphereResource#uuid() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Comment Edited] (WICKET-4723) tracking id retrieved in AtmosphereBehavior#onRequest() is always 0
[ https://issues.apache.org/jira/browse/WICKET-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13442680#comment-13442680 ] Sean Lin edited comment on WICKET-4723 at 8/28/12 7:21 AM: --- a related issue of atmosphere. https://github.com/Atmosphere/atmosphere/issues/544 AtmosphereResource#uuid() will be fixed to return the right tracking-id was (Author: linekin): a related issue of atmosphere. https://github.com/Atmosphere/atmosphere/issues/544 tracking id retrieved in AtmosphereBehavior#onRequest() is always 0 --- Key: WICKET-4723 URL: https://issues.apache.org/jira/browse/WICKET-4723 Project: Wicket Issue Type: Bug Components: wicket-atmosphere Affects Versions: 6.0.0-beta3 Reporter: Sean Lin Assignee: Emond Papegaaij jquery.atmosphere.js will always use 0 as initial tracking-id to send request, and then reassign it from server response. AtmosphereBehavior#getUUID() shouldn't return the tracking-id from request header, since the initial request's tracking-id is 0. The correct way to retrieve tracking-id is calling AtmosphereResource#uuid() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (WICKET-4729) atmosphere example will stop working if opening the same url in a different tab in the same browser
Sean Lin created WICKET-4729: Summary: atmosphere example will stop working if opening the same url in a different tab in the same browser Key: WICKET-4729 URL: https://issues.apache.org/jira/browse/WICKET-4729 Project: Wicket Issue Type: Bug Components: wicket-atmosphere Affects Versions: 6.0.0-beta3 Reporter: Sean Lin Assignee: Emond Papegaaij If the url of a running atmosphere example is copied and then opened in a different tab while the old one left open in the same browser, i.e. there are two atmosphere examples of the same url opened at the same time in a browser, one of them will stop working. I found the cause of this problem is that trackingPages in EventBus is using a BiMap. If there are different tracking-ids mapping to the same PageKey, one of the map entry will be removed. The simple solution would be replacing the BiMap with HashMap, but I think there might be reasons why BiMap is used here. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (WICKET-4723) tracking id retrieved in AtmosphereBehavior#onRequest() is always 0
[ https://issues.apache.org/jira/browse/WICKET-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13440128#comment-13440128 ] Sean Lin commented on WICKET-4723: -- After some tracing and testing, I found that AtmosphereResource#uuid() wil return wrong tracking-id under some circumstances. The uuid in AtmosphereResource is retrieved from response header X_ATMOSPHERE_TRACKING_ID, but it's set only when the request header X_ATMOSPHERE_TRACKING_ID is null or equals 0. This should be a issue of atmosphere, but currently to work with atmosphere 1.0.0.beta5, the only way to get the correct tracking-id I can see is via resource.getRequest().getAttribute(ApplicationConfig.SUSPENDED_ATMOSPHERE_RESOURCE_UUID); the resource above is AtmosphereResource. tracking id retrieved in AtmosphereBehavior#onRequest() is always 0 --- Key: WICKET-4723 URL: https://issues.apache.org/jira/browse/WICKET-4723 Project: Wicket Issue Type: Bug Components: wicket-atmosphere Affects Versions: 6.0.0-beta3 Reporter: Sean Lin Assignee: Emond Papegaaij jquery.atmosphere.js will always use 0 as initial tracking-id to send request, and then reassign it from server response. AtmosphereBehavior#getUUID() shouldn't return the tracking-id from request header, since the initial request's tracking-id is 0. The correct way to retrieve tracking-id is calling AtmosphereResource#uuid() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (WICKET-4727) ThreadContext should be detached before each subscribed page gets notified
Sean Lin created WICKET-4727: Summary: ThreadContext should be detached before each subscribed page gets notified Key: WICKET-4727 URL: https://issues.apache.org/jira/browse/WICKET-4727 Project: Wicket Issue Type: Bug Components: wicket-atmosphere Affects Versions: 6.0.0-beta3 Reporter: Sean Lin Assignee: Emond Papegaaij Since the event subscriptions may cross different sessions, before entering request cycles of notified page, the ThreadContext should be detached except application instance. In EventBus#post(Object event), ThreadContext.detach() should be placed inside the for-loop block of atmosphere resources, otherwise Session().get() may return previous page's session. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (WICKET-4723) tracking id retrieved in AtmosphereBehavior#onRequest() is always 0
Sean Lin created WICKET-4723: Summary: tracking id retrieved in AtmosphereBehavior#onRequest() is always 0 Key: WICKET-4723 URL: https://issues.apache.org/jira/browse/WICKET-4723 Project: Wicket Issue Type: Bug Components: wicket-atmosphere Affects Versions: 6.0.0-beta3 Reporter: Sean Lin Assignee: Emond Papegaaij jquery.atmosphere.js will always use 0 as initial tracking-id to send request, and then reassign it from server response. AtmosphereBehavior#getUUID() shouldn't return the tracking-id from request header, since the initial request's tracking-id is 0. The correct way to retrieve tracking-id is calling AtmosphereResource#uuid() -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Created] (WICKET-4724) the option name maxRequests is wrong in jquery.wicketatmosphere.js
Sean Lin created WICKET-4724: Summary: the option name maxRequests is wrong in jquery.wicketatmosphere.js Key: WICKET-4724 URL: https://issues.apache.org/jira/browse/WICKET-4724 Project: Wicket Issue Type: Bug Components: wicket-atmosphere Affects Versions: 6.0.0-beta3 Reporter: Sean Lin Assignee: Emond Papegaaij the option name should be maxRequest not maxRequests -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
