Book Image

Learning Play! Framework 2

By : Andy Petrella
Book Image

Learning Play! Framework 2

By: Andy Petrella

Overview of this book

<p>The Learning Play! Framework 2 has been created for web developers that are building web applications. The core idea is to focus on the HTTP features and to enable them through a simplification lens. Building a web application no longer requires a configuration phase, an environment setup, or a long development lifecycle - it's integrated!<br /><br />Learning Play! Framework 2 will enable any web developers to create amazing web applications taking advantage of the coolest features. It's the fastest way to dive into Play!, focusing on the capabilities by using them in a sample application. Although essentially Java based code, a Scala version is presented as well – giving an opportunity to see some Scala in action.<br /><br />After setting up the machine and learning some Scala, you will construct an application which builds from static to dynamic, before introducing a database. <br /><br />Then we'll focus on how data can be consumed and rendered in several ways. This will enable some real time communication through WebSocket and Server-Sent Event – on both server and client sides.</p> <p>The book will end with testing and deployment, which completes any web development project.</p>
Table of Contents (20 chapters)
Learning Play! Framework 2
Credits
About the Author
Acknowledgement
About the Reviewers
www.packtpub.com
Preface
Materials
Index

Ready, JSON, poll


In the earlier chapters, we built an application that mixed the notion of a chat and a forum. If we use it, we'll face some problems for sure; indeed, when we post a new message or image, the other users that are connected won't be notified unless they refresh their whole page. This kind of workflow is a pain in terms of performance and user experience. As it requires several users' actions, and because all data has to be provided by the server (which will give the same stuff again and again); think about big images that are loaded each time the application is refreshed. All of this tells us that such a workflow is not optimal at all. How are we going to tackle this? First we will use the ancestral polling system.

Polling is a system asking the server (or a bunch of services) the same resources repeatedly, and, normally, at a high rate (the higher it is, the better user experience you should have). So, it's trivial that it'll consume a lot of power, and often wasted because...