RE: Qamoos form: GET

["Ahmad Gharbeia" <ahmad at gharbeia dot org>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ahlan everybody,

The REST (REpresentational State Transfer) architectural principles
state that in order to build a usable and consistent web, the HTTP
verbs should be used according to the type of action intended.

GET, where parameters are passed on the URI, is suitable for creating
URIs that are bookmarkable, indexable by bots and embeddable under
anchors in markup. Compare with a search engine query, or shop
catalogue entry that you may bookmark or send to a friend.

On the other hand, POST is suitable for interfacing mechanisms that
alter data and should not be reinvoked arbitrarily. Adding a note to
a photo in a web album or a comment on a blog falls under this
category, in addition to suggesting an entry in a Qamoose.

As far as systems' design is concerned the "taking-in of suggestions"
IS a data change. Regardless of whether it is instantly reflected in
the database searchable by the public or not or not.

This is even more important with web services that it is for
server-to-human webs, and this what some APIs, like Flickr and
del.icio.us violate in some places.

The page Nadim referred to asserts this in its abstract.

Salam,
Ahmad Gharbeia

More: RestWiki: http://rest.blueoxen.net/cgi-bin/wiki.pl 


- -----Original Message-----
From: Nadim Shaikli [mailto:shaikli at yahoo dot com] 
Sent: Thursday, October 27, 2005 00:11
To: ahmad at gharbeia dot org
Cc: admin at arabeyes dot org
Subject: Re: Qamoos form: GET

As was noted by M.Sameer there is no difference [1] between the two
as far as QaMoose is concerned.  I also get the feeling that you
misunderstand what QaMoose is used for and what it intent was/is -
there is NO data changing occurring in QaMoose, its main function is
to display the contents of a database and to take-in suggestions to
be processed by a human for future integration.

[1] http://www.cs.tut.fi/~jkorpela/forms/methods.html

Salam.

 - Nadim


-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBQ2a6bG9Cp0X84DkFEQKpbACfVjF8wQLtWxli/vG6AQQKXd6MQ10AoOvC
z0aDVqbsDRzsYu3mdr5c+4cx
=WekC
-----END PGP SIGNATURE-----