This is a single archived entry from Stefan Tilkov’s blog. For more up-to-date content, check out my author page at INNOQ, which has more information about me and also contains a list of published talks, podcasts, and articles. Or you can check out the full archive.

Many people map the HTTP

Stefan Tilkov,

Many people map the HTTP verbs POST, GET, PUT, DELETE to Create, Read, Update, Delete (CRUD), which doesn’t really capture the semantics. So I found I like this analogy better:

Personally I am a fan of mapping the operations DELETE to cut, GET to copy, PUT to paste over, and POST to paste after. I know that others like to map the operations to the database CRUD model: POST to create, GET to retrieve, PUT to update, and DELETE to delete. It amounts to the same thing, except that the cut and paste view steers us more firmly away from record-based updates and into the world of freeform stuff to stuff and this to that data flows. Viewing the web as a document transfer system makes other architectures simpler, and makes them possible.

Not perfect, but certainly better.

On April 14, 2006 2:12 AM, Sam Mesh said:

Looks consistent with Ray Ozzie’s Live Clipboard for the Web… :)

On April 17, 2006 9:11 PM, ramtin said:

Interessting comparision. Once (for my master thesis) I have been reading a paper talking about an Algebra that is complete (in what terms ever) for text manipulation that is based on “cut, sopy and paste” .. unfourtunatly I don’t find the link anymore. It has possibly vanished in the “Library of Alexandria” called WWW.