4 ms·
For anyone interested in its claim of being reactive, as I was, the Play framework does not appear to support reactive programming [1]. From their samples and
by ghusbands 15y ago
For anyone interested in its claim of being reactive, as I was, the Play framework does not appear to support reactive programming [1].
From their samples and documentation, it looks like an event-driven server without any reactive aspects. I'm fairly sure they're mistakenly calling typical event-driven programming "reactive". This is backed up by the statements of Typesafe's CEO on the subject in an interview [2].
[1] http://en.wikipedia.org/wiki/Reactive_programming http://en.wikipedia.org/wiki/Reactive_programming
[2] http://www.infoq.com/news/2011/12/playframework-typesafestack http://www.infoq.com/news/2011/12/playframework-typesafestac...
- eweise 15y agoOr just read the play documentation https://github.com/playframework/Play20/wiki/Iteratees https://github.com/playframework/Play20/wiki/Iteratees
- ghusbands 15y agoWhich indeed is talking about stream processing. Play's stream processing uses iteratee IO to correct control inversions often suffered by networking libraries. However, Play does not offer automatic facilities for having variables (and interface) update when other variables change, as described in the Wikipedia article. For examples of reactive programming, see Knockout, batman.js and Ember.js (all primarily client-side).