first I'd like to apologize for our limited responsiveness to questions on this list over the course this week.
We'll try to work through the backlog over the course of the next days, so if your question has not yet received any response please hang in there.
Johannes and I spent a good part of this week with the Akka team up at their HQ in Uppsala (Sweden) for a workshop on a new and improved IO layer for Akka.
We all agreed that having a high-performance purely actor-based and no-dependency IO layer implementation is a very worthy cause for joining forces, sharing our experiences with the existing akka-io and spray-io implementations and coming up with the best design we currently can.
The new akka-io module is supposed to not only form the basis for a much improved akka-remoting solution as well as spray's HTTP stack, but also for your own protocol implementations. Additionally it is more general than the existing spray-io layer, since it will also (eventually) support non-TCP transports like UDP and file IO.
Currently we are jointly implementing the first (and—for the time being—most important) transport: TCP.
Once this is done we will of course want to put it to use as soon as possible, stay tuned as to when and how this will happen.
If anyone is interested in more details you can check out the first drafts of the developer documentation here:
and/or look at the code coming together on this branch:
We are very excited about this new stuff, it improves on spray-io's IOBridge implementation in a number of interesting ways (mostly with regard to foreseen latency and scalability), so we expect everything based on spray-can to become even faster.
Good times ahead… :)