Posted by Jerry Stuckle on 04/24/07 19:39

Vince Morgan wrote:
> "Vince Morgan" <vinhar@REMOVEoptusnet.com.au> wrote in message
> news:462e035a$0$22844$afc38c87@news.optusnet.com.au...
>> <davidkoree@gmail.com> wrote in message
>
> I forgot to offer any real context.
>
> print_r($_SESSION["f5s"]->_status); // -- bad one --
> /* This is bad one.
> * For example, if user has finished 3 steps, the $_SESSION["f5s"]-
>> _status should be:
> * { [step_1] => done, [step_2] => done, [step_3] => done }
> * But on some client computers the $_SESSION["f5s"]->_status may look
> like this:
> * { [step_1] => done, [step_3] => done }
>
> At this point the previously saved state of the session data could be
> reloaded. The session id would still be the same at this point, so the
> correct file to load can easily be idendified.
>
> * or this:
> * { }
> * If we refresh the browser on or more times, the $_SESSION["f5s"]-
>> _status would be complete (or uncomplete).
>
> If after reresh, and data is missing, samo. I'm not sure that JS would be
> required for this, though I beleive it would.
> Vince
>
>

Vince,

Since the session data is stored on the server and not the user's
computer, any access to the session data with that ID would show the
same thing. No browser refresh, and no way for it to get out of sync.

And no JS is required.

You may be thinking of cookies, where the data may be out of date on a
computer until the browser is refreshed.


--
==================
Remove the "x" from my email address
Jerry Stuckle
JDS Computer Training Corp.
jstucklex@attglobal.net
==================

[Back to original message]