Created by Alexander Daniel / @lachdrache
Sadek Drobi
A => BB => CA => C
Just a function: Request => Result
Is this enough?
RequestHeader =>
Iteratee[Array[Byte], Result]
You don't have to deal with Iteratee
the BodyParser takes care of it
If you want to do streaming stuff it is more complicated of course
most important thing about FP
Christopher Hunt
Make Play a great choice for JS development
a sbt plugin factored out of Play
handles the asset pipeline
Per default Rhino-based
Other JS engines like Node can be configured
parallel execution
incremental execution
Christopher recommends to start a Play project via Activator
WebJars will get CDN support in production
Yevgeniy Brikman
aka Jim
Play actions are just functions
Play has great streaming support
Showed how to implement Facebook BigPipe with Play
Inspiring how he composed the basic building blocks
James Roper
tech lead for Play
What is performance?
Play is about scalability
But reactive apps are slower that single-threaded because of context switching
Was mitigated Play 2.2 using a trampoline execution context which executes short-running operations on the same thread
If you have blocking operations in your app (e.g. JDBC) use separate execution context for these
Johan Andrén
Johan explained futures and actors with visual very attractive graphics
Great resource for understanding the concepts quickly
Conference web site at http://www.ping-conf.com
Videos of presentations available at http://www.ustream.tv/pingconf