CRUD SQL ReST / HTTP Unix
Create INSERT POST, PUT open(w+)
Read (Retrieve) SELECT GET read()
Update UPDATE POST open(), write()
Delete (Destroy) DELETE DELETE, POST unlink()

A RESTful web namespace design based on Plan 9

The central protocol the entire Plan 9 system is designed around is the 9P protocol. This is essentially a text-based protocol that is used for

HTTP Verbs Description Plan 9 Verbs Explanation
HEAD Asks for the response identical to the one that would correspond to a GET request, but without the response body. This is useful for retrieving meta-information written in response headers, without having to transport the entire content.
GET Requests a representation of the specified resource. Note that GET should not be used for operations that cause side-effects, such as using it for taking actions in web applications. One reason for this is that GET may be used arbitrarily by robots or crawlers, which should not need to consider the side effects that a request should cause. See safe methods below. Tread Rread size[4] Tread tag[2] fid[4] offset[8] count[4] size[4] Rread tag[2] count[4] data[count]
POST Submits data to be processed (e.g., from an HTML form) to the identified resource. The data is included in the body of the request. This may result in the creation of a new resource or the updates of existing resources or both.
PUT Uploads a representation of the specified resource.
DELETE Deletes the specified resource.
TRACE Echoes back the received request, so that a client can see what intermediate servers are adding or changing in the request.
OPTIONS Returns the HTTP methods that the server supports for specified URL. This can be used to check the functionality of a web server by requesting '*' instead of a specific resource.
CONNECT Converts the request connection to a transparent TCP/IP tunnel, usually to facilitate SSL-encrypted communication (HTTPS) through an unencrypted HTTP proxy.[5]