Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:92155
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.213.67 as permitted sender)
MIME-Version: 1.0
Sender: yohgaki@gmail.com
In-Reply-To: <570691E3.2080601@gmail.com>
References: <CAGa2bXYtQ_om8XSy6RPZeHxW8y9YMDcUf+Tug_++Mkk_+cr+mg@mail.gmail.com>
 <570691E3.2080601@gmail.com>
Date: Fri, 8 Apr 2016 13:46:38 +0900
Message-ID: <CAGa2bXa+h+GycqDZwnDcSq7jTtiuZy+3_F7Btt=6cBaV2tfVGg@mail.gmail.com>
To: Stanislav Malyshev <smalyshev@gmail.com>
Cc: "internals@lists.php.net" <internals@lists.php.net>
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [RFC][Discussion] Add session_create_id()
From: yohgaki@ohgaki.net (Yasuo Ohgaki)

Hi Stas,

On Fri, Apr 8, 2016 at 1:59 AM, Stanislav Malyshev <smalyshev@gmail.com> wrote:
>> Session ID can be non HEX strings. session_create_id() makes custom
>> session ID creation easier.
>> https://wiki.php.net/rfc/session-create-id
>>
>> Please note that the implementation was in the session.c years ago.
>> The patch enables and add test for it.
>
> I like the idea, but I would add a bit more details - where the ID comes
> from? Can I control it, and if so, how? Is uniqueness ensured and if
> not, how one is recommended to deal with it? Some code examples would
> help too. Some of it may be obvious to people who have been discussing
> session stuff for years now, but the RFC should be accessible to
> everybody, not just those participating is specific discussion. Ideally,
> one should be able to understand the RFC by knowing only what the PHP
> manual says and reading the RFC text.

Thank you for your comment.
Added more description,

https://wiki.php.net/rfc/session-create-id

If you feel missing something. Please let me know.

Regards,

--
Yasuo Ohgaki
yohgaki@ohgaki.net