|
|
Posted by Vince Morgan on 04/24/07 13:18
<davidkoree@gmail.com> wrote in message
news:1176881792.508187.177910@l77g2000hsb.googlegroups.com...
> I mean not about cookie.
> Does it have something to do with operating system or browser plugin?
> I appreciate any help.
>
Entering into this is perhaps the bravest thing I might ever had done in my
life.
What if one were to export the session data at intervals into files, or
overwrite a particular file at each step. The file/files being named in a
fashion that identifies their place in a hierachy, say a combination of
session id & time.
At the beginning of a new step, or say when there is a refresh perhaps, or
another appropriate time, the file data is compared against the contents the
$_session array.
If it's found that a step has been lost, or data is lost that can only be
explained by some failure, assume lost data, and reload the file back into
the session. This would effectively take the session back to a recently
saved state.
If these files were then deleted at a valid end of a session, or deleted
after a given period of time they should not become excessive.
If the session id and time were combined in the naming of the file then the
files should never be able to be retrieved accidently, thereby exposing
sensitive data.
Of course I am new to php, and internet programming in general and likely
have missed something in the scenario. However, it's something that
appears, to me, to offer a possible solution the the problem as it was
described by the OP.
Just a thought.
Vince
Navigation:
[Reply to this message]
|