|
|
Posted by Jerry Stuckle on 06/28/07 13:38
Sergei Shelukhin wrote:
> Umm, my last post was not intended for creating usual php vs asp
> flame, but for clarification, ASP.NET doesn't have session corruption
> problems for any storage mechanism available; for default in-proccess
> session the session (but not auth) "goes away" if something like web
> server restart happens, persistent storage doesn't have this problem
> too. And I never knew of any session corruption problems in ASP 3.0
> and never experienced it in my apps.
>
> Then, I cannot use another language - I have to use PHP for this
> project.
>
I have seen session corruption in .ASP. It's timing related, but it
does happen.
And if you have to use PHP, then I suggest you stop complaining and get
to programming. This is how PHP works. You want it to work another
way? Use another language.
Much of it has to do with the fact PHP stores its session data on the
file system. Among other things, this can help by surviving a webserver
restart. But it also means only one thread can have the file open at a
time.
--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================
Navigation:
[Reply to this message]
|