[
https://issues.apache.org/jira/browse/VYSPER-306?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13240404#comment-13240404
]
Stig Runar Vangen commented on VYSPER-306:
------------------------------------------
https://issues.apache.org/bugzilla/show_bug.cgi?id=51181
WebSocket support has been added to Tomcat 7.0.27. Lastest version for download
is 7.0.26.
http://java.dzone.com/articles/tomcat-websockets-html5
This guy made an implementation for Tomvat 7.0.14. Provided here as a Tomcat
patch.
Based on this, I think it is best to wait until the next Tomcat version is
officially released before starting work on a Tomcat implementation. I
initially thought of making a wrapper myself on top of the current Servlet API,
but this might not be possible.
> Websocket plugin too tightly bound to Jetty
> -------------------------------------------
>
> Key: VYSPER-306
> URL: https://issues.apache.org/jira/browse/VYSPER-306
> Project: VYSPER
> Issue Type: Bug
> Components: extension
> Affects Versions: 0.7
> Reporter: Stig Runar Vangen
> Assignee: Niklas Gustavsson
> Labels: extension, websocket
>
> I tried to integrate the websocket plugin into our system. Instead of setting
> up a jetty endpoint I wanted to use an existing server. This works fine if
> the server you want to integrate against is a Jetty server. In my case, the
> server is a Tomcat server. This resulted in Jetty-based errors when accessing
> the target address. The implementation should be server-independent, so that
> it could be used in more contexts.
--
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