In this chapter, we learned that Play! Framework 2 provides all the tools needed in order to work with remote third-party services. They represent their data either as XML or JSON, but it's not a big deal, thanks to the body parsing feature of Play! Framework 2.

We also took the opportunity to look at the WS API itself, the types that are important, and how and in which situations to use them (GET, POST, and so on). We're now ready to use any REST API easily.

Finally, we've seen what an asynchronous request in Play! Framework 2 is, and how to create it for long or potentially long tasks. It resulted in the performance of the application no longer being directly linked with the performance of remote third parties.

We ended up with a good overview of what Play! Framework 2 is able to offer us for the creation of amazing web applications, and how it is integrated with all layers composing a modern application, including not only the server side but also the client side.

However, what about the quality of the produced code or the exposed features? Are things also going to go so nicely when trying to test such fully-fledged web applications? We'll see in the next chapter that the answer to the second question is definitively "Yes", and that everything is in place to help us answer the first one.