Hey
I must admit - I get a little confused about when to use GET and
POST. I was reading this which confused me further:
Getting lazy with GET -- GET is for retrieving data; POST is for
setting it. Don't use GET when you know you shouldn't, even if you
think it will do no harm. GET operations change state, and links
that change state are confusing to users; most are accustomed to
links as guides to navigation, not function.
http://www.builderau.com.au/program/ajax/soa/The-Seven-Deadly-Sins-of-
AJAX-application-development/0,339028327,339274985,00.htm
My question: is it right to say that in a database/AJAX setting we
'should' use GET to SELECT data and POST to UPDATE or INSERT.
Also, I find the ideas about changing state interesting. I find
myself building more 'action-based' web sites where arguably
navigation and function are becoming one in the same (even to the
point where I'm seriously considering replacing traditional
navigation in favour of action prompts). I would have thought that a
user's understanding is that when you click a link or a button
something changes - the state. I would then have thought his
statement about changing state via links as sorta redundant. Or is he
just suggesting we make links that change state work more like how a
form is submitted (and surely defeating some of the benefits of this
whole AJAX thing). I would welcome some of your thoughts 'cos I'm
confused and I think that creating usable ajax-interfaces is vital to
it's long term success (and not just sizzle).
Have a good day!
Duncan
- - - - - - - - - - - - - - - - -
Sprocket Web Design
www.sprocket.co.nz
- - - - - - - - - - - - - - - - -
