qué les hablas mi lenguaje

Amsterdam.pm, Groningen.pm, AmsterdamX.pm, London.pm

20 minutes



REST api's are perfectly well designed to GET information from a server. With Content Negotiation, one can even let the server know what format the data should be represented, json, xml, html, or any other. It also allows the client to specify what language it accepts the data returned.

One resource, one URL!

Now, let server know what human language the client speaks..?

There is a way, within the restraints of the HTTP RFCs to update, modify or delete a resource that still fits in the REST principals and only needs one URL for that resource, without including format or language identifiers in the URL or parameters.

Welcome to HTTP Authoring.