[
https://issues.apache.org/jira/browse/CAMEL-16386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nikola Micić updated CAMEL-16386:
---------------------------------
Description:
I would like to propose a new component for RSocket.
The idea is to implement it in a similar way like already existing components
for HTTP and WebSocket. Currently RSocket in Java is implemented using Netty
via TCP and WebSocket protocols. Apache Camel already has component for Netty
which is also a good example from using as a model.
Uri of the new component could be like:
* rsocket:tcp://host:port?<options>
* rsocket:websocket://host:port?<options>.
was:
I would like to propose new component for RSocket that I would like to start
working on.
The idea is to implement it in a similar way like already existing components
for HTTP and WebSocket. Currently RSocket in Java is implemented using Netty
via TCP and WebSocket protocols. Apache Camel already has component for Netty
which is also a good example from using as a model.
Uri of the new component could be like:
* rsocket:tcp://host:port?<options>
* rsocket:websocket://host:port?<options>.
> camel-rsocket - Add a new Camel component for RSocket
> -----------------------------------------------------
>
> Key: CAMEL-16386
> URL: https://issues.apache.org/jira/browse/CAMEL-16386
> Project: Camel
> Issue Type: New Feature
> Affects Versions: Future
> Reporter: Nikola Micić
> Priority: Minor
>
> I would like to propose a new component for RSocket.
> The idea is to implement it in a similar way like already existing components
> for HTTP and WebSocket. Currently RSocket in Java is implemented using Netty
> via TCP and WebSocket protocols. Apache Camel already has component for Netty
> which is also a good example from using as a model.
> Uri of the new component could be like:
> * rsocket:tcp://host:port?<options>
> * rsocket:websocket://host:port?<options>.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
