From f399b0469176148805687db08ef80e97f71a3d33 Mon Sep 17 00:00:00 2001 From: Jeremy Ashkenas Date: Fri, 29 Jul 2011 10:06:25 -0400 Subject: [PATCH] some Markdown snuck in. --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index dfb49273..bc09bce5 100644 --- a/index.html +++ b/index.html @@ -2447,7 +2447,7 @@ var model = localBackbone.Model.extend(...);

References between Models and Views can be handled several ways. Some people like to have direct pointers, where views correspond 1:1 with - models (`model.view` and `view.model`). Others prefer to have intermediate + models (model.view and view.model). Others prefer to have intermediate "controller" objects that orchestrate the creation and organization of views into a hierarchy. Others still prefer the evented approach, and always fire events instead of calling methods directly. All of these style work well. @@ -2457,7 +2457,7 @@ var model = localBackbone.Model.extend(...); Batch operations on Models are common, but often best handled differently depending on your server-side setup. Some folks don't mind making individual Ajax requests. Others create explicit resources for RESTful batch operations: - `/notes/batch/destroy?ids=1,2,3,4`. Others tunnel REST over JSON, with the + /notes/batch/destroy?ids=1,2,3,4. Others tunnel REST over JSON, with the creation of "changeset" requests: