Re: Fixing halfway implemented session management - timestamp based session management OR remove session_regenerate_id()

From: Date: Sun, 25 Sep 2016 22:44:35 +0000
Subject: Re: Fixing halfway implemented session management - timestamp based session management OR remove session_regenerate_id()
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-96143@lists.php.net to get a copy of this message
Hi Thomas, On Mon, Sep 26, 2016 at 6:40 AM, Thomas Bley <mails@thomasbley.de> wrote: > why not have a new session module? those who want no change for existing applications keep the > old one, new projects can use the new one, those who want more security port their code to the new > one. e.g. use session2_start(), etc. If basic session module design has problems, I would write new one. However, the design is not the problem, but just implementation is not finished yet. There wouldn't much BC with timestamp. In fact, almost all apps will work without any problems with timestamped session management. I would rather deprecate/remove session_regenerate_id() if timestamped session management will not be implemented. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net

« previous php.internals (#96143) next »