I believe multi-part Json just doesn't make any sense from an service
consumer point of view, nor do i think any of the average gadget
developers would know how to do this from the top of their heads,
which creates a higher barrier of entry, so if that can be avoided i'd
give that correction to the spec a big +1
On the shindig side of things that would leave us with 2 paths to
batching which is 'slightly bothersome to code and maintain', but at
least usable for all the consumers of the service, and it also beats
having 3 batching code paths to maintain :)
-- Chris
On Jul 13, 2008, at 11:24 PM, Louis Ryan wrote:
A batching mechanism for JSON should not rely on multi-part.
