Naive question around support for Jetty Reactive support

[Peter Grazaitis]

Has anybody tried leveraging the Jetty Reactive class to wrap the HttpClient in CometD? Ultimately trying to incorporate Spring WebClient support.

[Simone Bordet]

Hi,

On Fri, Apr 14, 2023 at 5:12 PM Peter Grazaitis <pgraz...@gmail.com> wrote:
>
> Has anybody tried leveraging the Jetty Reactive class to wrap the HttpClient in CometD? Ultimately trying to incorporate Spring WebClient support.

Spring WebClient already supports Jetty Reactive HttpClient.

Can you detail what problems you have?

--
Simone Bordet
---
Finally, no matter how good the architecture and design are,
to deliver bug-free software with optimal performance and reliability,
the implementation technique must be flawless. Victoria Livschitz

[Peter Grazaitis]

Well, I had pulled code around Salesforce's EMP Connector and it looks like that references CometD 4.0.4 which had LongPollingTransport hardcoding the non-reactive Jetty HTTP Client. In searching the latest version of CometD seems to have deprecated that class and I believe I need to dig around and see how to upfit the EMP Connector.  If you have any good documentation around that you could point me to that would be great!

Thanks,

-Pete G

[Simone Bordet]

Hi,

On Sat, Apr 15, 2023 at 3:46 AM Peter Grazaitis <pgraz...@gmail.com> wrote:
>
> Well, I had pulled code around Salesforce's EMP Connector and it looks like that references CometD 4.0.4 which had LongPollingTransport hardcoding the non-reactive Jetty HTTP Client.

You still don't say why you need to wrap `HttpClient` into "reactive".
Jetty's HttpClient is fully non-blocking, so you don't need any
"reactive" if you don't plan to use the reactive APIs (because they
will be hidden by CometD and possibly by EMP).

--
Simone Bordet
----
http://cometd.org
http://webtide.com
Developer advice, training, services and support
from the Jetty & CometD experts.