Hi Spring fans! In this installment of Spring Tips we answer the question, "how do I propagate state across asynchronous, reactive execution pipelines?" speaker: Josh Long / starbuxman
Hi Josh, I got one example like XPathFactory instantiation XPathFactory.newInstance(), which is not thread safe hence we can use Context to store the factory here. But I can see in your examples the Context is shared among the different threads, should we have to manage ourself to make it available on the same thread only ?
I think you're missing some interesting opportunities. Spring Data uses it for transaction demarcation. Spring Security uses it for propagation of principal information. HTH
Hi Josh, I don't see a lot of examples online using Reactive Websockets. Currently am using Websockets with UnicastProcessor for my chat room application. Can this use-case be dealt with RSockets or is RSockets just for intercommunication between Microservices? Pls, advise.
hi bud -check out this example. the important bit is that you need a `WebSocketHandlerAdapter,` a `WebSocketHandler`, and a `SimpleUrlHandlerMapping`. github.com/joshlong/reactive-revolution/blob/master/main/rsocket-service/src/main/java/com/example/service/ServiceApplication.java#L110 as for RSocket, well, your browser isn't going to understand RSocket by default. you can use a JS library to speak RSocket on top of WebSockets, but it's an extra layer. You could use RSocket to handle a chat application, though, absolutely. You'd also get some nice benefits including the ability to then more naturally consume that cha API from any RSocket client, headers ("metadata"), Spring Security JWT/Simple authentication , and more
