ByteCode.News
Submit RSS Atom Sign in

Back to the channels

#java

  1. hassoon 'morning
  2. enoq I was able to prototype a bit further (regarding mvc or webflux): using either solution, you can shoot yourself in the foot; I was able to figure out how to get all the benefits of VTs combining them with Kotlin Coroutines for parallel http requests; turns out runBlocking supports virtual threads out of the box, with the exception that you need to wrap blocking Java APIs in a VT thread dispatcher (similar to how webflux requires those
  3. enoq on a blocking thread that supports VTs)
  4. enoq since parallel http requests seem to be the most pressing issue and those work fine on mvc, I'll go with that
  5. dreamreal +1