* Joel Bernstein j...@fysh.org [2009-11-15 16:30]:
No no no! Allow the client and server to negotiate what content
to serve for the resource identified. As a URI to a resource
which may vary according to many dimensions,
/path/to/some/content is fine.
GET /path/to/content HTTP/1.1
On Wed, Nov 18, 2009 at 9:55 AM, Aristotle Pagaltzis pagalt...@gmx.dewrote:
* Joel Bernstein j...@fysh.org [2009-11-15 16:30]:
No no no! Allow the client and server to negotiate what content
to serve for the resource identified. As a URI to a resource
which may vary according to many
