Mark Nottingham wrote: > -----Original Message----- > From: Mark Nottingham [mailto:[EMAIL PROTECTED] > Sent: Monday, December 10, 2007 3:15 AM > To: Steven Lees > Cc: Brian Smith; 'Atom-Syntax' > Subject: Re: Tombstones > > Please, please don't use a media type parameter for this; it works > fine for the first extension or two that wants to do this, and scales > horribly after that. > > Cheers, > > > On 07/12/2007, at 9:09 AM, Steven Lees wrote: > > >> The most obvious way to do it would be to add a parameter to the > >> application/atom+xml mime type, and use that parameter along with a > >> strong "q" parameter in an Accept header: > >> > >> Accept: application/atom+xml;type=feed;FeedSync=1.0;q=1, > >> application/atom+xml;q=0.9 > > > > Thanks, seems like a good suggestion. Presumably the client could > > specify: > > > > Accept: application/atom+xml;type=feed;FeedSync=1.0;q=1 > > > > if it only wants the feed with tombstones. And then on the return > > trip, the server uses the same Content-Type: > > > > Content-Type: application/atom+xml;type=feed;FeedSync=1.0 > > > > One potential drawback is that in both cases, the entity returned > > is actually a valid Atom feed. It might be nice to have the > > "tombstone-ness" reflected in a way that doesn't alter the Content- > > Type.
Thanks for the guidance. Is there a longer form explanation anywhere of how/why this breaks down? And is there any existing header that is better suited to this purpose? Steven
