|
|
Posted by Jerry Stuckle on 06/26/07 22:34
Sergei Shelukhin wrote:
> Huh? ASP.NET doesn't have this problem, and neither does ASP. As far
> as I remember Perl doesn't have this problem either, I don't remember
> how I stored the session back then tho. If for example I want to store
> some token between several pages it's pretty impractical to do so in a
> database, taking care of the timeout/cleanup and uniqueness code too,
> the fact that there's a variable that either locks up parallel
> requests or is readonly is pretty illogical from my fresh point of
> view :)
>
> The strangest thing is that the app I'm now maintaining and improving
> was written by an actual PHP programmer who used session in this way
> and somhow tricked users into believing that slow search query locking
> up their profile editing is ok 0_o
>
Hmmm, you're right - ASP doesn't lock it. But then ASP has known
problems with session corruption when the session is being accessed by
multiple windows. I can only assume ASP.NET, if it works the same way,
has the same problem.
And IIRC, Perl also has a problem with multiple windows accessing the
same session. But the last time I had that problem was a while ago;
most of my new programming is in PHP nowadays. So perhaps that
"problem" has been fixed.
And you can store them in a database or you can store them in a file
(PHP's default).
Or, if you can't stand the way PHP handles sessions, you can, of course,
use a different language.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|