Re: session_reset() and session_abort() to send errors

Hi, > This function is useful for session save handlers that do not lock > session data. Example is memcached. This function could be used > re-read session data to mitigate over written session data with unlock > session data. > > Andrey, just because you don't think of usage, it does not mean it does not > mean unneeded or not useful. You are better to ask the reason behind why > first. > Good library should have defined API for specific tasks, too. You also has > misunderstanding about why delayed deletion for session_regenerate_id() > is mandatory. Yasuo ... There's no misunderstanding, I just have a disagreement with you about that issue and I'm tired of arguing over that. Let's just keep session_regenerate_id() in it's own thread, ok? But speaking of mandatory: locks are mandatory, so how are non-locking handlers an argument in all of this? Also, I didn't just question if there's a use case, I'm questioning if it is safe to use session_reset() at all. Re-reading doesn't imply discarding currently open resources and complerely re-initializing the session and from what I see - that's exactly what the function does, or am I missing something? Cheers, Andrey.