camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Richard Kettelerij (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-7316) client-side websocket component
Date Thu, 27 Mar 2014 09:43:14 GMT

    [ https://issues.apache.org/jira/browse/CAMEL-7316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13949094#comment-13949094
] 

Richard Kettelerij commented on CAMEL-7316:
-------------------------------------------

[~ay] This is a nice contribution. A websocket client based on async-http-client would definitely
come in handy, especially for users who are already using async-http-client for HTTP.

I'm just thinking since this component extends the camel-ahc component wouldn't it be better
to rename it to *camel-ahc-websocket*. This is much clearer for end users. Also camel-ws is
to generic for my taste, ws can refer to either websocket or webservice.

> 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)

Mime
View raw message