camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Aki Yoshida <elak...@gmail.com>
Subject thoughts on the camel-websocket component
Date Tue, 10 Sep 2013 10:00:29 GMT
I have been looking into the websocket component and  I was wondering
about a few things.

First of all, I would like to make the component use the framework's
servlet if it's running in e.g., an OSGi container like karaf that has
jetty or another container that uses geminiweb/tomcat. I was using
Atmosphere to have the framework's servlet container picked up in both
environments.

I saw ticket CAMEL-5353 "camel-atmosphere - A new component for
portable websocket integration" and this seems to imply the
introduction of a new atmosphere specific component that might go
beyond the websocket functionality. Or is this intended for just a new
websocket component? I think Claus created this ticket when there was
a question in the mailing list about making the component work with
tomcat. I don't know its scope and status  and if someone is working
on this.

Another thing I was wondering about is that we should also have a
client-side websocket so that we can post data to an external
websocket. As the current websocket's producer mode writes back to the
server side websocket, we will need a new syntax for this usage, maybe
using the ws URL. This could be used in both the producer and consumer
modes as in the websocket component.

If you could comment on this, that would be very appreciated.

Thanks.
regards, aki

Mime
View raw message