W3C home > Mailing lists > Public > public-appformats@w3.org > January 2008

RE: Proposal for a way to avoid a round-trip on every POST when dealing with large numbers of URIs

From: Close, Tyler J. <tyler.close@hp.com>
Date: Thu, 31 Jan 2008 17:00:43 +0000
To: John Panzer <jpanzer@acm.org>, Ian Hickson <ian@hixie.ch>
CC: "public-appformats@w3.org" <public-appformats@w3.org>
Message-ID: <C7B67062D31B9E459128006BAAD0DC3D074F651071@G6W0269.americas.hpqcorp.net>

I'm having trouble understanding the proposed solution. Could someone provide an alternate explanation or a sample protocol exchange?

Thanks,
--Tyler

John Panzer wrote:
> Ian Hickson wrote:
> > ...
> > Problem: Some HTTP-based protocols, like AtomPub, require
> the use of a
> > large number of distinct URIs. For example, adding a tag or
> category to a
> > series of posts on a blog using AtomPub requires one
> non-GET request per
> > blog post. While this is prohibitively expensive anyway
> when done from a
> > high-latency network like GSM or EDGE, it is still somewhat
> painful to
> > require two round trips per non-GET request in cases like
> this even on
> > low-latency high-bandwidth connections, and therefore
> deserves further
> > consideration.
> >
> > Proposed Solution: The proposed solution allows one new
> optional header
> > for OPTIONS responses. The header contains a path.
> >
> > ...
> >
> This proposal effectively addresses the performance & server side
> scalability concerns I had with the cross-domain access
> control mechanism.
>
> Thanks,
> John Panzer
> Tech Lead/Manager, Google (Blogger, OpenSocial, & Friends)
>
>
>
>
Received on Thursday, 31 January 2008 17:01:51 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:56:21 UTC