ml
> may
> be what I am looking for. Will any consumer that is non-blocking work or
> just Jetty?
>
> Thanks,
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Non-blocking-HTTP-based-Microservices-tp5791879p5791890.html
> Sent
It does look like: http://camel.apache.org/asynchronous-processing.html may
be what I am looking for. Will any consumer that is non-blocking work or
just Jetty?
Thanks,
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Non-blocking-HTTP-based-Microservices
er above so that we have true non-blocking.
>
>
>
> --
> View this message in context:
> http://camel.465427.n5.nabble.com/Camel-Non-blocking-HTTP-based-Microservices-tp5791879p5791886.html
> Sent from the Camel - Users mailing list archive at Nabble.com.
>
that we have true non-blocking.
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Non-blocking-HTTP-based-Microservices-tp5791879p5791886.html
Sent from the Camel - Users mailing list archive at Nabble.com.
EST DSL. I see where Spring has support for ListenableFuture &
DeferredResult for consumer interfaces. Is there a Camel equivalent? This
would significantly reduce the need for non-blocking platforms such as
Node.js.
Thanks,
--
View this message in context: http://camel.465427.n5.nabble.
com/
ture &
DeferredResult for consumer interfaces. Is there a Camel equivalent? This
would significantly reduce the need for non-blocking platforms such as
Node.js.
Thanks,
--
View this message in context:
http://camel.465427.n5.nabble.com/Camel-Non-blocking-HTTP-based-Microservices-tp5791879.html
Sent
