I'm also digging the Hijax approach. It really fits in line with my general view of web standards as modularizing/separating the different tasks of web development - content, structure, presentation, behavior, and now server interaction.
Quote:
|
Originally Posted by MikeMackay
Jeremy Keith is a big standardista so he will always take the route he deems right, but I don't think there is anything 'semantic' so to speak about your situation and whether using GET or POST really makes a difference, although JK might argue otherwise?
|
Agreed. Right after I posted that I read through Chapter 5 (Hijax) and his first example uses GET to request data from the server.
Maybe I'm just hung up on the words. I've been doing PHP for a while and never really thought about the difference much - I've always thought of it more as:
GET: transferring small amounts of info to the server, encoded in a URL.
POST: transferring larger amounts of info to the server, submitted from a form.
Really, either request is always sending something to the server. It just depends on how that data is sent to the server.