camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Claus Ibsen <claus.ib...@gmail.com>
Subject [DISCUSS] - camel-websocket component
Date Mon, 11 Jun 2012 09:38:15 GMT
Hi

In Camel 2.10 we introduce a new component: camel-websocket.
Its currently based on Jetty, and thus requires jetty to be used.

In recent time the component was enhanced to support SSL with websocket as
well. That change brings in a lot of code that was
copied directly from the existing camel-jetty component.

So I wonder if we should consider

1)
Merge the code from camel-websocket into camel-jetty, as its all Jetty
based.
This avoid duplicated code,
This allows to share port numbers with http services and websocket.
Currently that is not possible as its 2 different components.

2)
Change the component name from websocket, so its part of jetty, eg

from("websocket:foo")
    becomes
from("jetty:ws:foo")

The current jetty component supports
- http
- https

So adding websocket is a matter of having
- ws
- wss

3)
In the future there will be other websocket implementations/components in
Camel. For example the Atmosphere framework seems to be a great framework
for that. As well with future releases of the JEE spec may introduce
websocket support from a spec point of view.
So having camel-websocket that is tied to Jetty seems to tie the "generic"
websocket name to a specific implementation (jetty).



Any thoughts?



-- 
Claus Ibsen
-----------------
FuseSource
Email: cibsen@fusesource.com
Web: http://fusesource.com
Twitter: davsclaus, fusenews
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message