On Tue, May 10, 2005 at 11:58:35AM +0200, Mario Ruggier wrote: > Is it not the client that issues the GET or POST... or the DELETE. But, > which web clients ever know when to do this? (The METHOD attribute of > FORM only accepts GET and POST, at least for html 4...)
I think the hardcore REST people have their heads a little in the clouds. It's not possible to make most browsers use PUT or DELETE, AFAIK. > So, such a link_to means that all GETs are issued as POSTs, and > translated to a GET by the server? But that loses too much client > functionality... the convenience of having a bookmarkable url, for > example ?!? > > I must be missing something here. The idea is to allow something like "<a href=..." that uses POST (e.g. via javascript trickery). One problem with a form is that it is a block-level element and can be tricky to fit into available space. BTW, "idempotent" is not actually enough. "Safe" is actually the key phrase in the specification. Neil _______________________________________________ Quixote-users mailing list Quixote-users@mems-exchange.org http://mail.mems-exchange.org/mailman/listinfo/quixote-users
