On 12/13/06, Sylvain Hellegouarch <[EMAIL PROTECTED]> wrote:
> Consider GData apps. Their docs aren't clear (tsk, tsk!) about the > use of a media type when inserting entries[1], but if they're doing it > properly then their services should be keying off of > "application/atom+xml", and so will break if that's changed. > And? Should a status quo be better on the long term?
I was just disagreeing with Tim's assertion that nothing will break.
> Other server implementations should have the same issue, of course. So please explain me what a server currently does upon receiving an Atom feed on a POST to a collection that only (app:)accept (atom:)entry(ies)? Returning a 415 error code seems like the wrong option since the media-type is perfectly valid. So what should servers do? Should they pick-up randomly one of the entries part of the feed? How should UA deal with the returned message?
AIUI, that's undefined, and will remain so no matter what is decided here. I don't understand what that has to do with a new media type breaking existing servers though. Of course, APP isn't finished yet, and so technically we shouldn't be worrying about breaking implementations that "jumped the gun". But given that an alternative exists which shouldn't break those servers, why not use it when there's no apparent downside? Mark.
