Re: [Phplib-users] new Session4 changes

[Giancarlo <gia...@na...>]

PHP4 Serialization and URL rewriting (trans_sid) are valuable indeed, 
file savehandler could be accomodated, but propagation is faulty and 
has no abstraction and is rigidly tied to all the rest. As I said, if I 
could choose pieces of it...


> G> Why not 'preissue' a fair enough number of 'second_half of session
> G> info', and save them in the session, so  that only one among those can
> G> be appended or cookie_appended? Use once
> G> random md5 digests. Would that  be really bullet_proof..
> 
> It does not resolve the problem, because that "second part" is saved
> with the session, and we have access to this part since we know the
> SID.

I meant the 'second half' can be used only once and must be chosen among 
a fair enough batch of pregenerated ones.


> Yes, but sometimes the personal info should present on [almost] every
> page, if the user is authenticated. And the search bot travels the
> same pages as other users, they may have auth info while the bot
> may not (and they will see slightly different pages). It's a common
> case.

What I said is that, upon certain not so uncommomd prerequisites, it can 
be difficult to have a twin mode-falback_mode that fit all cases, from 
the bot to the cookie_only authed user...

Gian