James Holderness wrote:
> Joe Cheng wrote:
> > Ah, I was not aware of the Vary field. Brian, never mind
> > about caching issues, as they are addressed by Vary.
>
> I thought the problem was that Vary wasn't always well
> supported by proxies. I don't remember the issues exactly, but
> I'm sure Mark did some research into this.
If content negotiation is going to be used at all, then "Vary: Accept"
header is more likely to work correctly than anything else besides
"Vary: Content-Encoding".
Regardless of whether a media type parameter is added for FeedSync,
content negotiation should not be required. I think it is just an issue
of whether we want to have:
<!-- register a media type parameter for FeedSync -->
<link rel='alternate' href='...'
type='application/atom+xml;FeedSync=1.0'/>
Or:
<!-- register an Atom link relation for FeedSync -->
<link rel='FeedSync' href='...'
type='application/atom+xml'/>
Or both:
<link rel='FeedSync' href='...'
type='application/atom+xml;FeedSync=1.0'/>
Or neither:
<!-- Don't register anything -->
<link rel='http://feedsync.org/blah' href='...'
type='application/atom+xml'/>
- Brian
