3 ms·
Well, if you're talking about alternatives that do asynchronism, Comet and Web Sockets well, the most convenient framework I ever used is Play 2.1 The framewor
by bad_user 13y ago
Well, if you're talking about alternatives that do asynchronism, Comet and Web Sockets well, the most convenient framework I ever used is Play 2.1
The framework is said to be reactive, meaning that you can build components that react to events asynchronously. The architecture is completely awesome, as Akka actors are baked in and the protocols are modelled with Futures and Iteratees, an FP concept for sane I/O. Things like serving unending streams of data and responding to client events using async I/O are in the very foundations of the framework, instead of being taked on later. People using Node.js or Tornado or whatever, don't know what they are missing.
See their docs on the subject:
- for Scala: http://www.playframework.com/documentation/2.1.1/ScalaAsync http://www.playframework.com/documentation/2.1.1/ScalaAsync
- for Java: http://www.playframework.com/documentation/2.1.1/JavaAsync http://www.playframework.com/documentation/2.1.1/JavaAsync
- euroclydon 13y agoI've heard it's revolutionary! How do you host Play in production?
- bad_user 13y agoWe are using Amazon's EC2 for a huge-traffic web service (because ELB with auto-scalling has been working great for us) and Heroku for auxiliary services. Deployment to Heroku works out of the box btw.
- euroclydon 13y agoI mean, which web server? What is the built-in start/stage server built on? Can you place it behind Nginx?
- playing_colours 13y agoThe built-in server is Netty, a non-blocking one, and you can deploy your Play webapp as a stand-alone server, or use Nginx, Apache etc. http://www.playframework.com/documentation/2.1.1/HTTPServer http://www.playframework.com/documentation/2.1.1/HTTPServer