Comments on: PATCHing and BATCHing http://www.subbu.org/blog/2008/02/patching-and-batching Wed, 08 Feb 2012 05:16:45 +0000 hourly 1 http://wordpress.org/?v=3.3.1 By: subbu.org http://www.subbu.org/blog/2008/02/patching-and-batching/comment-page-1#comment-210 subbu.org Mon, 25 Feb 2008 10:22:22 +0000 http://wp.subbu.org/2008/02/patching-and-batching/#comment-210 <strong>Batching - Back to Basics</strong> In response to my post on PATCHing and BATCHing, John Panzer made a very valid comment. How can you design a resource that lets you add a contact record, then retrieve contacts 11-20 out of 100, in one HTTP round trip, assuming that you don't know a pr... Batching – Back to Basics

In response to my post on PATCHing and BATCHing, John Panzer made a very valid comment. How can you design a resource that lets you add a contact record, then retrieve contacts 11-20 out of 100, in one HTTP round trip, assuming that you don’t know a pr…

]]> By: Subbu Allamaraju http://www.subbu.org/blog/2008/02/patching-and-batching/comment-page-1#comment-209 Subbu Allamaraju Sun, 24 Feb 2008 14:52:24 +0000 http://wp.subbu.org/2008/02/patching-and-batching/#comment-209 I agree with your comment. Better URI is only the first step that I would take. To solve the above use case, assuming that a failure to add the contact record does not stop contact retrieval, we will need a generic batch service. I agree with your comment. Better URI is only the first step that I would take. To solve the above use case, assuming that a failure to add the contact record does not stop contact retrieval, we will need a generic batch service.

]]> By: John http://www.subbu.org/blog/2008/02/patching-and-batching/comment-page-1#comment-208 John Sun, 24 Feb 2008 13:50:08 +0000 http://wp.subbu.org/2008/02/patching-and-batching/#comment-208 Agreed with your comments, but they only go so far. Canonical example: How can you design a resource that lets you add a contact record, then retrieve contacts 11-20 out of 100, in one HTTP round trip, assuming that you don't know a priori whether or not your addition is going to affect the resource you want to retrieve (contacts 11-20)? Agreed with your comments, but they only go so far. Canonical example: How can you design a resource that lets you add a contact record, then retrieve contacts 11-20 out of 100, in one HTTP round trip, assuming that you don’t know a priori whether or not your addition is going to affect the resource you want to retrieve (contacts 11-20)?

]]> By: Mike Amundsen http://www.subbu.org/blog/2008/02/patching-and-batching/comment-page-1#comment-207 Mike Amundsen Fri, 15 Feb 2008 17:44:25 +0000 http://wp.subbu.org/2008/02/patching-and-batching/#comment-207 Excellent post. BATCHing over HTTP stretches too many of the reasonable constraints. It's much better to expose new URIs in cases where things like this are needed. Excellent post. BATCHing over HTTP stretches too many of the reasonable constraints. It’s much better to expose new URIs in cases where things like this are needed.

]]>