Hi all, It's an exciting time for Akka with the imminent release of akka-http (as announced in 2013 in this thread <https://groups.google.com/forum/#!searchin/akka-user/Akka-HTTP/akka-user/sMB8tjYPOLA/ywU2G9baqwgJ> and more recently reaffirmed in this other thread <https://groups.google.com/forum/#!searchin/akka-user/Akka-HTTP/akka-user/bIdV9HlUHkg/R_zeAOZFdI4J>)! If I'm not mistaken, that would be the latest milestone:
https://github.com/akka/akka/tree/releasing-akka-stream-and-http-experimental-1.0-M2 That's awesome news... but this kind of transition always pose a challenge on new projects: should one use the new (experimental) milestone release or stick to the original components for a few months and then have to go through a migration (that can potentially impact system design) on a "newborn"? Or go the other way around and risk using something that's not stable? I realise there's no easy answer besides the standard "only use stable releases for production". But on the other hand, how far are we from a production release of akka-http? How stable is the milestone 2? How painful will be the migration from software based on current spray.io to the new aka-http? So, what have you guys been doing when confronted with these choices? Has anyone evaluated these 2 systems recently? Thanks for your thoughts on this. Cheers, Richard -- >>>>>>>>>> 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
