Mencoba mengembalikan lagi diskusi REST
Saya baru nemu snippet ini di spesifikasi draft Atom Publishing Protocol :
4.3
<http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-16.html#rfc.section.4.3>
Control
and Publishing
<http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-16.html#codeisdata>
The Atom Publishing Protocol uses HTTP methods to author Member
Resources as follows:
* GET is used to retrieve a representation of a known Resource.
* POST is used to create a new, dynamically-named, Resource.
When the client submits non-Atom-Entry representations to a
Collection for creation, two Resources are always created - a
Media Entry for the requested Resource, and a Media Link Entry
for metadata about the Resource that will appear in the
Collection.
* PUT is used to edit a known Resource. It is not used for
Resource creation.
* DELETE is used to remove a known Resource.
The Atom Protocol only covers the creating, editing, and deleting of
Entry and Media Resources. Other Resources could be created, edited
and deleted as the result of manipulating a Collection, but the
number of those Resources, their media-types, and effects of Atom
Protocol operations on them are outside the scope of this specification.
Since all aspects of client-server interaction are defined in terms
of HTTP, [RFC2616]
<http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-16.html#RFC2616>
should be consulted for any areas not covered in this specification.
http://bitworking.org/projects/atom/draft-ietf-atompub-protocol-16.html
Yah, begitulah "definisi" REST secara praktis.......
Kalo sudah make 4 method HTTP tersebut sesuai dengan fungsinya... Bisa
dibilang aplikasi tersebut sudah selangkah (?) menuju REST
Apalagi dengan mengimplementasikan Atom Publishing Protocol, sudah
dipastikan aplikasi tersebut REST-oriented karena Atom sendiri
RESTful... (ato RESTish?)
--
Hendy Irawan
www.hendyirawan.com