note 108627 deleted from function.session-destroy by danbrown

Note Submitter: bee kay two at em ee dot com ---- I love it when the documentation for function named X says this function doesn't do X. If you want to do X, use (this long bit of code). And a question, if this does not actually destroy the current session (since it can be restarted), or its cookies, or its globals, what exactly does it destroy? What good is it? Not being argumentative, I really mean what does it destroy? What situation would I call this function, and NOT do the other stuff in (long bit of code)? And while some others posted how to "really" do X in this case by mucking with the file system folder the session stuff is USUALLY stored in, one should not even know how sessions are implemented to use sessions. And for safety and security, the system should not LET you open the folder it depends on to do session control. UNSECURE. So, how about someone add a new function, that actually removes all traces of the current session securely? session_really_destroy() ? Anyone?