Hi
I will do a new review round tomorrow morning.
Thanks
Regards
JB
On Aug 8, 2017, 13:04, at 13:04, Christian Schneider
wrote:
>I now adapted the package names as well as the maven coordinates. All
>files should now also have the apache headers.
>I also made sure the
I now adapted the package names as well as the maven coordinates. All
files should now also have the apache headers.
I also made sure the build now works without any running mqtt or kafka
server.
I would be happy about a quick review of the current status. If there
are no objections then I
In camel there is now a camel-reactive-streams component that bridges
camel and reactive-streams specs so the integration with the proposed
subproject should be easy.
There is also a camel-reactor and - I hope soon - a camel-rxjava2
component to provide an implementation of the
I definitely like the idea. Camel-rx is for RxJava 1.x which is not based
on the reactive streams API (RxJava 2.x, however, is based on that API).
On 19 July 2017 at 06:51, Guillaume Nodet wrote:
> At first glance, it looks similar related to http://camel.apache.org/rx.
>
Scope
I recently experimented with reactive streams and built a small
component framework on top of this spec.
See https://github.com/cschneider/reactive-components
The goal is to have a small API that can encapsulate a protocol and
transport. The code using such a reactive component