search

yrift / jwebsocket

Automatically exported from code.google.com/p/jwebsocket
0 stars 0 forks source link

Request to use Jetty as WebServer and embed jWebSocket into a Jetty App #76

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago 
Jetty is supposed to support websockets, here we want to use the Jetty engine 
in a way like we embed the jWebSocket server into Tomcat but with using Jetty's 
WebSocket engine instead of ours.

The goal here is to really upgrade an existing http connection on port 80 to a 
websocket connection.

Original issue reported on code.google.com by fivefeetfurther@gmail.com on 14 Oct 2010 at 2:55

GoogleCodeExporter commented 9 years ago

Original comment by fivefeetfurther@gmail.com on 14 Oct 2010 at 4:20

GoogleCodeExporter commented 9 years ago 
Started to evaluate Jetty integration because we have users that are not 
granted to open 8787 but port 80 or 8080 only and hence need to use the http 
"upgrade" of the WebSocketProtocol to go throught their firewall/proxy. Jetty 
provides that and so we started evaluation here. We are starting with Jetty 
8.0.0.M1 here.

Original comment by fivefeetfurther@gmail.com on 28 Oct 2010 at 9:47

GoogleCodeExporter commented 9 years ago 
Already made good progress here. We pushed tgis a bit because Jetty allows us 
to get rid of the separate 8787 port. Jetty also supports SSL! This has been 
test already and thus will be published with v0.11 now!

Original comment by fivefeetfurther@gmail.com on 10 Nov 2010 at 11:08

GoogleCodeExporter commented 9 years ago 
[deleted comment]
GoogleCodeExporter commented 9 years ago 

Awesome !!! any target date for v 0.11 ?
Thanks and appreciate all the hard work.

Original comment by nivedit....@gmail.com on 10 Nov 2010 at 3:46

GoogleCodeExporter commented 9 years ago 
are there any further updates on this ??

Original comment by nivedit....@gmail.com on 13 Jan 2011 at 5:36

GoogleCodeExporter commented 9 years ago 
There's a separate project jWebSocketJetty available now in the Downloads / 
Nightly Build Section of jWebSocket.org now.

Original comment by fivefeetfurther@gmail.com on 27 Feb 2011 at 2:30

GoogleCodeExporter commented 9 years ago 
Remaining ISSUES: You currently cannot yet append additional arguments via 
<path>/;arg to the URL when using Jetty. Here we need to switch to use 
/<path>&arg=value... and fix this for the other engines!

We also want to use the NIO SSL connector from Jetty in one of the next 
releases.

Original comment by fivefeetfurther@gmail.com on 24 Apr 2011 at 10:08

GoogleCodeExporter commented 9 years ago 
Insert listener into Jetty App to remain compatible with other engine demos.
Also support custom protocols in Jetty beside pure token approach.
Consider creating shared (demo) classes for all engines.

Original comment by fivefeetfurther@gmail.com on 24 Apr 2011 at 10:12