[jira] [Updated] (CAMEL-8594) Camel and ReactiveX/RxJava
[ https://issues.apache.org/jira/browse/CAMEL-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jyrki Ruuskanen updated CAMEL-8594: --- Description: 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 ObservableExchange sequences. This arrangement could greatly benefit both projects and simplify the Camel codebase as well. was: 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, frontends and a variety of extensions to RX, and routes/pipelines would be built as ObservableExchange sequences. This arrangement could greatly benefit both projects and simplify the Camel codebase as well. 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 ObservableExchange 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)
[jira] [Updated] (CAMEL-8594) Camel and ReactiveX/RxJava
[ https://issues.apache.org/jira/browse/CAMEL-8594?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jyrki Ruuskanen updated CAMEL-8594: --- Description: 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, frontends and a variety of extensions to RX, and routes/pipelines would be built as ObservableExchange sequences. This arrangement could greatly benefit both projects and simplify the Camel codebase as well. was: 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 and a variety of extensions to RX, and routes/pipelines would be built as ObservableExchange sequences. This arrangement could greatly benefit both projects and simplify the Camel codebase as well. 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, frontends and a variety of extensions to RX, and routes/pipelines would be built as ObservableExchange 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)
