Backbone Marionette.js - A Serious Progression by David Sulc - 2014.mobi

Backbone.Marionette.js: A Serious Progression
This book takes up where the Marionette introduction book left off. It will use an actual API back-end developed for this book, that will be easily adaptable to your framework. Dowload the sample (NOT AVAILABLE YET!) to see how the ContactManager application is configured to connect to the remote API.
If you'd rather use your own API, each chatper details the relevant specifications your API must conform to.

Written in the same easy to follow style as its predecessor, you should have no trouble following along as you enhance the ContactManager application. Here are some of the topics we'll cover:

using remote APIs
dealing with legacy APIs
converting data received from the API using parse
massaging data with toJSON before sending it to the API
handling server-side responses
properly reacting to server-side error codes (e.g. 404 Not Found)
processing server-side validation errors
usign deferreds or success/error callbacks
handling validation with Backbone.Validator
model-only validation
form & model validation (error display)
pagination using Backbone.Paginator
explore pagination through client- and server-side pagination
developing a general-purpose view to display paginated data (with automatic pagination controls maangement)
managing the pagination controls
managing the URL and routes
data relationships
manage nested collections "by hand"
using Backbone.associations to handle associations
i18n
using polyglot
authentication
strategies to consider
handling session timeouts
handling authorization
wrapping third-party APIs: see how we wrap GitHub's API so we can interact with Git repositories using only Backbone models and collections
implementing a custom Backbone.sync function from start to end
refreshing client-side data: how to manage cases where the data on the server has changed before a user sends data updates
improving memory management
defining methods on prototypes
using listenTo
starting/stopping sub-applications