* Matt S Trout <[EMAIL PROTECTED]> [2007-05-18 16:30]: > On Fri, May 18, 2007 at 03:29:20PM +0200, A. Pagaltzis wrote: > > * Matt S Trout <[EMAIL PROTECTED]> [2007-05-18 14:30]: > > > I prefer to have my code wired up fairly explicitly for GET > > > vs. POST but that's more an obsession with the HTTP and URI > > > standards than any practical concern. > > > > The Rails crew learned the painful way that there can be very > > practical concerns indeed when you get these wrong… :-) > > > > (For those who don’t know: using POST where GET would be > > appropriate just costs you cacheability and thus scalability; > > using GET where POST would be appropriate can cost your users > > their data.) > > Right, but you can deal with that just by checking > $c->req->method. > > I distinguish explicitly between query and body params as well, > which is overkill for some situations.
I know you know what you’re doing. :-) I wasn’t explaining it to *you*, I just didn’t want people who may not yet know better to get the impression that this is ivory tower stuff with no real- world impact. Regards, -- Aristotle Pagaltzis // <http://plasmasturm.org/> _______________________________________________ List: [email protected] Listinfo: http://lists.rawmode.org/mailman/listinfo/catalyst Searchable archive: http://www.mail-archive.com/[email protected]/ Dev site: http://dev.catalyst.perl.org/
