[
https://issues.apache.org/jira/browse/CAMEL-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949159#comment-13949159
]
Aki Yoshida edited comment on CAMEL-7316 at 3/27/14 11:19 AM:
--------------------------------------------------------------
Hi Richard,
Thank you for your comment. I was unsettled for the component naming and the
protocol name :-).
I was not sure if we should provide a component that is not specific to its
implementation (i.e., which could change in the future) or a component that is
specifically bound to its implementation.
Initially, the code was not using camel-ahc directly but using the ahc client
library. But after I made a minor refactoring in camel-ahc, I could use
camel-ahc as the base component.
Since the current code is specific to ahc and its configuration is embedded in
the endpoint (as ahc configuration), that means we are necessarily exposing ahc
specificness to its endpoint configuration. So, I agree that we should have
"ahc" name in the part of the component and protocol name.
If no one objects the name change, I can rename the component and protocol name
accordingly.
thanks.
regards, aki
was (Author: ay):
Hi Richard,
Thank you for your comment. I am unsettled for the component naming and the
protocol name :-).
I was not sure if we should provide a component that is not specific to its
implementation (i.e., which could change in the future) or a component that is
specifically bound to its implementation.
Initially, the code was not using camel-ahc directly but using the ahc client
library. But after I made a minor refactoring in camel-ahc, I could use
camel-ahc as the base component.
Since the current code is specific to ahc and its configuration is embedded in
the endpoint (as ahc configuration), that means we are necessarily exposing ahc
specificness to its endpoint configuration. So, I agree that we should have
"ahc" name in the part of the component and protocol name.
If no one objects the name change, I can rename the component and protocol name
accordingly.
thanks.
regards, aki
> client-side websocket component
> -------------------------------
>
> Key: CAMEL-7316
> URL: https://issues.apache.org/jira/browse/CAMEL-7316
> Project: Camel
> Issue Type: New Feature
> Reporter: Aki Yoshida
> Assignee: Aki Yoshida
> Fix For: 2.14.0
>
>
> Introducing a client-side websockert component that can connect to a remote
> websocket and transfer data in both directions in the duplex mode.
> It uses AHC and its endpoint can be used in the producer role to write to the
> socket or in the consumer role to read from the socket.
> This is the cliend-side component described in the following dev@camel
> message:
> http://camel.465427.n5.nabble.com/update-of-websocket-td5740578.html#a5742396
--
This message was sent by Atlassian JIRA
(v6.2#6252)
