Presenting in Dallas: Play Framework, HTML5 and Java

Tomorrow (December 12, 2012) I will be presenting in Dallas at the JavaMUG about Client/Server Apps with Play Framework, HTML5 and Java. Here is the session abstract:

The web application landscape is rapidly shifting back to a Client/Server architecture. This time around, the Client is JavaScript, HTML, and CSS in the browser. The tools and deployment techniques for these types of applications are abundant and fragmented.

This session will teach you how to pull together jQuery, LESS, Twitter, Bootstrap, and some CoffeeScript to build the Client. The Server could be anything that talks HTTP, but this session will use the Play Framework.

I hope to see you there!

This entry was posted in HTML5, Java, Play Framework. Bookmark the permalink. Post a comment or leave a trackback: Trackback URL.
  • David Clark

    I caught your talk at the DFW Users Group. I enjoyed it and learned a lot. Thank you for your time.

    I didn’t get a chance to ask a question at the end of the meeing about CDN’s. The architecture you presented of had all dynamic content/data on a centralized server (or server) while the static content could live anywhere, including on a CDN. The idea was that a CDN would provide better performance for clients because they could download static content from a server closer to them. My question is: how much of a performance boost does this provide the average web app that utilizes the architecture you presented?

    I ask because it seems to me that with because the static content is only downloaded once (or rarely), the CDN doesn’t buy much. And the more the static content is, well static, the less it buys you. Browser caching alone will seem to make the CDN redundant in these cases. Sure, the initial download is slow, but after that, everyone performs the same since they are always going back to the main server(s).

    • http://www.jamesward.com James Ward

      Thanks David. I’m glad the talk was useful for you. It’s a good question. There are many layers to web optimization. One of those is transport. A CDN can make a very big difference in how long it takes to download content. I provide a little more detail about this in this post: http://www.jamesward.com/2012/08/08/edge-caching-with-play2-heroku-cloudfront

      But ultimately it’s best to do some tests to see where you should spend time on optimization. There are tools out there that check web performance from all over the globe. But if your users aren’t all over the globe, then that probably isn’t a top priority for where to spend your time optimizing.

  • nilesh

    Do you have a video recording of your talk?



  • View James Ward's profile on LinkedIn