|
|
Posted by Chung Leong on 03/02/06 03:43
Carl wrote:
> Like already being logged in when you browse the same site in another
> window or tab? I would think thats a good thing.
I assure you that those who use the feature are very much dependent on
it. When I reply to posts on Google Group, for example, I frequently
would flip back to the previous screen in a different so I can see
what's been said already. On occasions I would open still another tab
when I want to cite a previous thread.
> My advice would be the opposite, don't pass data in the URL unless you
> have a good reason to, and there often are good reasons.
It really isn't a matter of making a choice between GET and session.
It's about using something in the manner that it's designed for.
Session variables are designed for persistency. If that's what the
situation calls for, then use them. If not, then use something better
suited.
HTTP is a stateless protocol (by and large). A GET operation is
understood to be side-effect-less (i.e. read-only). When you stuff URL
parameters into the session, you're violating this basic assumption,
and predictably, bad things happen: bookmarking goes bust, tab-browsing
behaves weirdly, search engines can't spider your site, etc.
Navigation:
[Reply to this message]
|