2013년 11월 27일 수요일

The Protocol Semantics of HTTP

There are rules. In a RESTful system, clients and servers interact only by sending each other messages that follow a predefined protocol.
The HTTP standard defines eight different kinds of messages, These four are the most commonly used:

GET
Get a representation of this resource.

DELETE
Destroy this resource.

POST
Create a new resource underneath this one, based on the given representation.

PUT
Replace this state of this resource with the one described in the given representation.

These two methods are mostly used as a client explores an API:

HEAD
Get the headers that would be sent along with a representation of this resource, but no the represntation itself.

OPTIONS
Discover with HTTP methods this resource respons to.

The other two methods defined in the HTTP standard, CONNECT and TRACE, are only used with HTTP proxies. I won’t be covering them.

I recommend that API designers consider a ninth HTTP method, defined not in the HTTP standard but in a supplement, RFC 5789:

PATCH
Modify part of the state of this resource based on the given representation. If some bit of resource state is not mentioned in the given representation, leave it alone.

PATCH is like PUT, but allows for fine-grained changes to resource state.

댓글 1개:

  1. 윤창이형 반가워요...
    RESTful 정보 검색하다 여기까지 왔네요.
    애기 아빠 되신거 축하드리고요. 좋은 정보 많이 공유해 주세요.

    답글삭제

ETL 솔루션 환경

ETL 솔루션 환경 하둡은 대용량 데이터를 값싸고 빠르게 분석할 수 있는 길을 만들어줬다. 통계분석 엔진인 “R”역시 하둡 못지 않게 관심을 받고 있다. 빅데이터 역시 데이터라는 점을 볼때 분산처리와 분석 그 이전에 데이터 품질 등 데이...