Its an interesting question: what does it mean to "restore an
applications state"?
Given that there is a Web server, loading a PHP module, that then sucks
up a PHP script and then spits out a stream of HTTP to the Web
browser.... in a sense, that HTTP stream is your serialization.
Saving and restoring state makes sense with stateful applications, but
on the Web, which is basically stateless (ignoring the backend stuff),
there is little need for it. Maybe it is even dangerous....
don´t know what apps you´re creating, but mine are holding several links (alias/reference) to other objects like parser-,database-,several special-object-,desgin- and so on obejects.
They all hold a lot (more or less) of a data and *finally* stream it to a browser.
Initializing them all takes a lot of time (msecs) and the apps could be quite a lot faster if their state can be remembered during a local session (user session) and a global session (website session).
What i want to serialize has not much to do with the generated stream of HTTP data. (It includes data which will/could be displayed sometimes too, sure).
The web is not basically different from non-web space. If you care about security encrypt the data.
0.2 EUR
regards
--
o----------0-¬---------O-·---¬----o---®-----o o O ° .
| http://www.kiffen.de | pRoteçt y0ur bRaín |0 O ° ¤ °
·
0°·³°²'²³-¹'³´³°^°³~³²³°'³²²¨³²^³¹³²°²³`³º³°Þ °
o © ° . ·
| psychedelic experience | gott@kiffen.de | O ° o °
o-¬--o--0-----©-·--O-----o-----0-¤----------o 0 ° · ° . ¤ ·