camel-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jyrki Ruuskanen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CAMEL-8594) Camel and ReactiveX/RxJava
Date Fri, 03 Apr 2015 18:15:53 GMT

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

Jyrki Ruuskanen commented on CAMEL-8594:
----------------------------------------

Right, could the page be under https://cwiki.apache.org/confluence/display/CAMEL/RX?

Proving the concept could start with developing the camel-rx module further to see how far
we can go with the current components, and CamelContext and Exchange objects. Then we'll see
if RX pipeline could be an option in Camel 2, requires architecture changes which means Camel
3, or is just not feasible.

> Camel and ReactiveX/RxJava
> --------------------------
>
>                 Key: CAMEL-8594
>                 URL: https://issues.apache.org/jira/browse/CAMEL-8594
>             Project: Camel
>          Issue Type: Wish
>            Reporter: Jyrki Ruuskanen
>            Priority: Minor
>
> To me, ReactiveX and Camel looks like a perfect match. I'm wondering if all Camel routes
could in future (Camel 3?) be based on RX?
> Camel would bring the components, front-ends and a variety of RX extensions, and routes/pipelines
would be built as Observable<Exchange> sequences.
> This arrangement could greatly benefit both projects and simplify the Camel codebase
as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message