Comments on Abstractioneer: I'd Rather Batch than Fight

The biggest difference is in the case of browsers ...

2008-02-24T23:04:00.000-08:00

The biggest difference is in the case of browsers hosting AJAX apps. A pipelining extension requires new browsers, something that takes years. An agreement on an HTTP based protocol however can be deployed in a matter of weeks.

John, That's true, BUT you're talking about defini...

2008-02-24T22:06:00.000-08:00

John,

That's true, BUT you're talking about defining something new anyway - and hoping people adapt. It makes more sense (to me) to extend something known other than creating something further from what we have - that is, it's easier to extend pipelining than create multiparting batch requests, IMHO.

Lior

@Liorsion -- pipelining only allows GET and HEAD, ...

2008-02-24T13:35:00.000-08:00

@Liorsion -- pipelining only allows GET and HEAD, eliminating the most compelling use case. (Read only batching can already be achieved by defining an appropriate read-only feed and retrieving that.) Also, it's not turned on out of the box in FF or IE so it's effectively not available to browser-based clients.

Hi,Didn't quite follow how this batching method is...

2008-02-23T21:51:00.000-08:00

Hi,

Didn't quite follow how this batching method is better than pipelining - which is much more wildly supported. We use more BW with pipeline due to the HTTP, but we use a lot less CPU on both sides (client/server) since we don't need to parse.. What's the point then?

Lior