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-j
Hi Claus,
I completely agree on your proposition as we reuse pieces of code between
the different (same) camel components (jetty, websocket but also cometd) as
they increase "maintenance" costs.
Point 1) --> +1 to merge camel-jetty, camel-websocket and camel-cometd
The most important thing will
This does make a lot of sense to me. websocket is really a standard for
which there could be multiple implementations. Thus, the component name
really should be the implementation, not the standard. Otherwise you get
into the whole "camel-http" issue again of having multiple things that CO
+1 from my point of view.
Christian
Sent from a mobile device
Am 11.06.2012 18:52 schrieb "Daniel Kulp" :
>
> This does make a lot of sense to me. websocket is really a standard for
> which there could be multiple implementations. Thus, the component name
> really should be the implementation
+1
On Jun 12, 2012, at 3:56 PM, Christian Müller wrote:
> +1 from my point of view.
>
> Christian
>
> Sent from a mobile device
> Am 11.06.2012 18:52 schrieb "Daniel Kulp" :
>
>>
>> This does make a lot of sense to me. websocket is really a standard for
>> which there could be multiple imp
+1
Regards
JB
On 06/11/2012 11:38 AM, Claus Ibsen wrote:
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 l
Hi
I have logged a ticket about this
https://issues.apache.org/jira/browse/CAMEL-5364
I don't think we got the time to work on this now. So I have scheduled it
for 2.11.
Also I can see that camel-websocket needs to mature a bit more, for example
the last commit by Charles is a bit "hacky".
And I
being commented out:
org.apache.camel.component.websocket.WebsocketComponentTest
which is a bit "ugly" as well. If no volunteer, I could try to fix them but
not before this weekend.
Babak
--
View this message in context:
http://camel.465427.n5.nabble.com/DISCUSS-camel-websocket-co
ll. If no volunteer, I could try to fix them but
> not before this weekend.
>
> Babak
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/DISCUSS-camel-websocket-component-tp5714283p5714404.html
> Sent from the Camel Development mailing list archive at Nabble.com.
>
I could try to fix them
>> but
>> not before this weekend.
>>
>> Babak
>>
>>
>> --
>> View this message in context:
>> http://camel.465427.n5.nabble.com/DISCUSS-camel-websocket-component-tp5714283p5714404.html
>> Sent from the Camel Development mailing list archive at Nabble.com.
>>
>
--
View this message in context:
http://camel.465427.n5.nabble.com/DISCUSS-camel-websocket-component-tp5714283p5714450.html
Sent from the Camel Development mailing list archive at Nabble.com.
10 matches
Mail list logo