AI-powered
podcast player
Listen to all your favourite podcasts with AI-powered features
Spring's Reactive Approach to Synchronized Blocks
I'm sure the Spring team are well aware of all the potential implications of this here. We've just removed a lot of blocking synchronized bits in the code base over the last decade or so, writ large. So for example, files aren't, there's no NIO files. There's async file channels, whatever they're called, but they're not NIO. For socket IO, you have Pulling - it's the thing where you can get notified based on when it is time to write that.