[
https://issues.apache.org/jira/browse/WICKET-4724?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440192#comment-13440192
]
Emond Papegaaij commented on WICKET-4724:
-----------------------------------------
This is indeed wrong, however I'm wondering if this option is still needed. I
added it because with long-polling, the browser stopped connecting after 60
cycles. Is this still the case? If so, I think this should be fixed in
Atmosphere itself, because with long-polling you do not want the browser to
stop connecting, not even after 100000 cycles. Atmosphere should differentiate
between failed connections and normal disconnections.
> 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
