You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Sean Lin (JIRA)" <ji...@apache.org> on 2012/08/22 12:56:38 UTC
[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] [Commented] (WICKET-4723) tracking id retrieved in
AtmosphereBehavior#onRequest() is always 0
Posted by "Sean Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Commented] (WICKET-4723) tracking id retrieved in
AtmosphereBehavior#onRequest() is always 0
Posted by "Sean Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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] [Commented] (WICKET-4723) tracking id retrieved in
AtmosphereBehavior#onRequest() is always 0
Posted by "Emond Papegaaij (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440209#comment-13440209 ]
Emond Papegaaij commented on WICKET-4723:
-----------------------------------------
I've added a fallback in case the uuid is "0". For a real solution, I need Jeanfrancois Arcand to explain how this is supposed to work in Atmosphere.
> 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] [Comment Edited] (WICKET-4723) tracking id retrieved in
AtmosphereBehavior#onRequest() is always 0
Posted by "Sean Lin (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-4723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=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