[jira] [Resolved] (WICKET-5007) Allow to configure the transport

["Emond Papegaaij (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/WICKET-5007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Emond Papegaaij resolved WICKET-5007.
-------------------------------------

    Resolution: Duplicate

I think the best way would be to allow passing parameters to atmosphere. This should be done through a central settings class. I'll see if I can come up with a solution for the next release, which should be in about 3 weeks.
                
> Allow to configure the transport
> --------------------------------
>
>                 Key: WICKET-5007
>                 URL: https://issues.apache.org/jira/browse/WICKET-5007
>             Project: Wicket
>          Issue Type: Improvement
>          Components: wicket-atmosphere
>            Reporter: Andrei Badea
>            Assignee: Emond Papegaaij
>
> We would like to avoid websockets in our applications, because we do not consider the technology stable and mature enough. We will use streaming instead.
> Could you please make the default transport configurable somehow? Right now it is hardcoded in jquery.wicketatmosphere.js. With the current configuration, every page load triggers two Atmosphere requests: a websockets one and a streaming one.
> I'm happy to provide a patch, but need some guidance on how you'd prefer this done. Where would this configuration go in Java code? On the EventBus perhaps, since it's such a core component?

--
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