> >[EMAIL PROTECTED] wrote: >>> Jan Algermissen wrote: >>> >>>> So, upon a >>>> >>>> GET /feed/media-links/3 HTTP/1.1 >>>> Accept: image/* >>>> >>>> should the server respond with a temporary redirect? >>> Again, 406 Not Acceptable. Why do you want this behaviour? >> >> To enable non-Atom-aware user agents to access the entry and because I >understand the media entry to be a negotiation point for the media, its >metadata, maybe the metadat in RDF, the media in another format (e.g. gif vs. >jpeg).... > >That's surely the issue. To do this you'd be /at least/ APP-aware and >then some - you have to know you're dealing with an APP endpoint and not >just an HTTP one.
Aside from my question, this is intersting: I thought APP was a subset of HTTP, not an extension to it. So APP defines a contract[1] that goes beyond HTTP - seems counter to the original idea of APP, or? Am I missing something here? Jan [1] Set aside the semantics of links to enable traversal, of course. But the MIME type I discover at runtime via Content-Type and I am still just communicating to an HTTP endpoint. As for the the negotiation point, that's interesting >but it's invention. Plus. There's the error cases/defaulting; what >should happen when sending audio/* to an image/* type. There's also >security/transparency - by design sending the wrong media type to a >resource to get it to serve another resouce /seems/ broken/dangerous to >me. Sorry, I'm unconvinced by this. > >cheers >Bill >
