What kind of web container (if any are you using)? I'd say using ask and blocking on it is still an improvement with pre 3.0 servlets.
With asynchronous servlets you can push the AsyncContext down in a message or use as in the ask future's onComplete callback. With other frameworks (Netty, Jetty, Akka HTTP, non blocking 3.1 servlets, etc.) things will be even better. There's just no need to use ask in other places, That's all. In other words it makes perfect sense to use it for the integration point between your existing blocking code and your new Akka based code and slowly change code to or add new asynchronous code. -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to akka-user+unsubscr...@googlegroups.com. To post to this group, send email to akka-user@googlegroups.com. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
