Browse Library
Sign In Start Free Trial
Close icon Search icon
Account
Browse Library Sign In Start Free Trial

Add to playlist

Create a Playlist

Modal Close icon
You need to login to use this feature.
  • Book Overview & Buying Mastering play framework for scala
  • Table Of Contents Toc
Mastering play framework for scala

Mastering play framework for scala

By : Saxena
3.2 (10)
Buy this Book
close
close
Mastering play framework for scala

Mastering play framework for scala

3.2 (10)
By: Saxena
Buy this Book

Overview of this book

This book is intended for those developers who are keen to master the internal workings of Play Framework to effectively build and deploy web-related apps.
Table of Contents (15 chapters)
close
close
close
Preface
Icon
Preface
Icon
What this book covers
Icon
What you need for this book
Icon
Who this book is for
Icon
Conventions
Icon
Reader feedback
Icon
Customer support
Lock Free Chapter
1
1. Getting Started with Play
Icon
1. Getting Started with Play
Icon
Venturing into the world of Play
Icon
Summary
2
2. Defining Actions
chevron up
Icon
2. Defining Actions
Icon
A dummy Artist model
Icon
Actions
Icon
Request body parsers
Icon
Extending a parser
Icon
Exploring the results
Icon
Asynchronous Actions
Icon
Content negotiation
Icon
Filters
Icon
Action composition
Icon
Troubleshooting
Icon
Summary
3
3. Building Routes
Icon
3. Building Routes
Icon
Introduction to Play routes
Icon
Reverse routing
Icon
Assets
Icon
Configuring route definitions
Icon
Configuring request parameters
Icon
Troubleshooting
Icon
Summary
4
4. Exploring Views
Icon
4. Exploring Views
Icon
Diving into Scala templates
Icon
Generating forms
Icon
Internationalization
Icon
Scala templating in Play
Icon
Troubleshooting
Icon
Summary
5
5. Working with Data
Icon
5. Working with Data
Icon
Introducing models
Icon
JDBC
Icon
Anorm
Icon
Slick
Icon
ReactiveMongo
Icon
The Cache API
Icon
Troubleshooting
Icon
Summary
6
6. Reactive Data Streams
Icon
6. Reactive Data Streams
Icon
Basics of handling data streams
Icon
Iteratees
Icon
Enumerator
Icon
Enumeratees
Icon
Summary
7
7. Playing with Globals
Icon
7. Playing with Globals
Icon
GlobalSettings
Icon
The life cycle of an application
Icon
The request-response life cycle
Icon
Summary
8
8. WebSockets and Actors
Icon
8. WebSockets and Actors
Icon
An introduction to WebSockets
Icon
WebSockets in Play
Icon
Actor Model
Icon
Introducing Akka Actors
Icon
WebSocket using Iteratee
Icon
WebSocket using Actors without Iteratees
Icon
Closing a WebSocket
Icon
Troubleshooting
Icon
Summary
9
9. Testing
Icon
9. Testing
Icon
The setup for writing tests
Icon
Unit testing
Icon
Dissecting PlaySpecification
Icon
Unit testing a controller
Icon
Functional testing
Icon
Summary
10
10. Debugging and Logging
Icon
10. Debugging and Logging
Icon
Debugging a Play application
Icon
Experimenting in a Scala console
Icon
Logging
Icon
Play's logging API
Icon
Log configuration in Play
Icon
Summary
11
11. Web Services and Authentication
Icon
11. Web Services and Authentication
Icon
Calling web services
Icon
OpenID
Icon
OAuth
Icon
Summary
12
12. Play in Production
Icon
12. Play in Production
Icon
Deploying a Play application
Icon
Configuring for production
Icon
Enabling SSL
Icon
Using a load balancer
Icon
Troubleshooting
Icon
Summary
13
13. Writing Play Plugins
Icon
13. Writing Play Plugins
Icon
Plugin definition
Icon
Plugin declaration
Icon
Exposing services through plugins
Icon
Tips for writing a plugin
Icon
Summary
14
Index
Icon
Index

Exploring the results

In Play, the response to a request is a result. A result has two components: the response header and the response body. Let's look at a simple example of this:

def plainResult = Action {
  Result( 
    header = ResponseHeader(200, Map(CONTENT_TYPE -> "text/plain")), 
    body = Enumerator("This is the response from plainResult method".getBytes())
  )
}

Notice that we used an enumerator for the response body. An enumerator is a means to provide data to an iteratee. We will discuss these in detail in Chapter 6, Reactive Data Streams.

Apart from this, a result has additional functions that equips us with better means to handle response headers, sessions, cookies, and so on.

A result can send JSON, XML, and images as a response, apart from a String content. An easier way of generating a result is to use the result helpers. A result helper is used for most of the HTTP response status. As an example, let's see how the TODO Action that comes built in with Play is implemented...

CONTINUE READING
83
Tech Concepts
36
Programming languages
73
Tech Tools
Icon Unlimited access to the largest independent learning library in tech of over 8,000 expert-authored tech books and videos.
Icon Innovative learning tools, including AI book assistants, code context explainers, and text-to-speech.
Icon 50+ new titles added per month and exclusive early access to books as they are being written.
Mastering play framework for scala
End of Section 2
Next Section
notes
bookmark Notes and Bookmarks search Search in title playlist Add to playlist font-size Font size

Change the font size

margin-width Margin width

Change margin width

day-mode Day/Sepia/Night Modes

Change background colour

Close icon Search
Country selected
Close icon Your notes and bookmarks

Confirmation

Modal Close icon
claim successful
Order Page Read Now

Buy this book with your credits?

Modal Close icon
Are you sure you want to buy this book with one of your credits?
Close
YES, BUY

Submit Your Feedback

Modal Close icon
Modal Close icon
Modal Close icon