Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:86948 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 51700 invoked from network); 29 Jun 2015 21:38:13 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 29 Jun 2015 21:38:13 -0000 Authentication-Results: pb1.pair.com header.from=yohgaki@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=yohgaki@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.160.181 as permitted sender) X-PHP-List-Original-Sender: yohgaki@gmail.com X-Host-Fingerprint: 209.85.160.181 mail-yk0-f181.google.com Received: from [209.85.160.181] ([209.85.160.181:35423] helo=mail-yk0-f181.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 51/25-25761-FBAB1955 for ; Mon, 29 Jun 2015 17:38:08 -0400 Received: by ykdy1 with SMTP id y1so127050234ykd.2 for ; Mon, 29 Jun 2015 14:38:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc:content-type; bh=hhkREIVdJyqEDZndbCqyhzdI1uYrVJt4cnRkp7OqfhI=; b=0LB0A83qR2Z6fmYTnsu58ievb7KSDEt7W3ZB0V2OXKa4pnjyqDfj3pLhfKOpd27aQM PgSbau4P0MfbC9J1+JaekPhFAX6u+wXWemOVGfpUOchmCW1CfddudS/EGSEN/S0F8xF8 roIsK8Vw7ojqzNxrR7vVU+3qvPXXdpoeNyyooxgTTU0Ae67UUkwWe8U/VUz4L7dIUMa1 68DuaBM8Zm06LLHma99x7wVXC23oyxjKLzzcLEIARmoV0cDcSGSo7REGPnb4o1V0xB51 2EdBuxWzk3a7Vjrl2ejXnOu+Q1upwaAaUkcZO5sghJEj38bmWoXLk8ETqtybVCZl1Vrn PIjg== X-Received: by 10.129.98.198 with SMTP id w189mr12489575ywb.32.1435613885149; Mon, 29 Jun 2015 14:38:05 -0700 (PDT) MIME-Version: 1.0 Sender: yohgaki@gmail.com Received: by 10.129.48.135 with HTTP; Mon, 29 Jun 2015 14:37:25 -0700 (PDT) In-Reply-To: <02be01d0b26e$469d3940$d3d7abc0$@belski.net> References: <02be01d0b26e$469d3940$d3d7abc0$@belski.net> Date: Tue, 30 Jun 2015 06:37:25 +0900 X-Google-Sender-Auth: XRVs4dFDrAh4JRVAHpF21XOTtEs Message-ID: To: Anatol Belski Cc: Hannes Magnusson , Kalle Sommer Nielsen , Internals , Anatoliy Belsky , Dmitry Stogov , Nikita Popov , Ferenc Kovacs , Xinchen Hui Content-Type: multipart/alternative; boundary=001a114713b8a8b6000519aee711 Subject: Re: [PHP-DEV] Headsup: PHP7 feature freeze From: yohgaki@ohgaki.net (Yasuo Ohgaki) --001a114713b8a8b6000519aee711 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hi Anatol, On Mon, Jun 29, 2015 at 10:19 PM, Anatol Belski wrote: > > -----Original Message----- > > From: yohgaki@gmail.com [mailto:yohgaki@gmail.com] On Behalf Of Yasuo > > Ohgaki > > Sent: Friday, June 26, 2015 1:58 PM > > To: Hannes Magnusson > > Cc: Kalle Sommer Nielsen; Internals; Anatoliy Belsky; Dmitry Stogov; > Nikita > > Popov; Ferenc Kovacs; Xinchen Hui > > Subject: Re: [PHP-DEV] Headsup: PHP7 feature freeze > > > > Hi all, > > > > On Fri, Jun 26, 2015 at 12:56 PM, Yasuo Ohgaki > wrote: > > > > > Hi Hannes, > > > > > > On Fri, Jun 26, 2015 at 12:51 PM, Yasuo Ohgaki > wrote: > > > > > >> On Fri, Jun 26, 2015 at 10:48 AM, Hannes Magnusson < > > >> hannes.magnusson@gmail.com> wrote: > > >> > > >>> Why do you think its undocumented? > > >>> http://php.net/manual/en/sessionhandler.create-sid.php > > >>> > > >> > > >> Rename discussion was there. And I explicitly discussed "it's > > >> undocumented and it violates CODING_STANDARDS", but it was added > > >> recently (after the discussion I suppose). > > >> > > >> [yohgaki@dev session]$ svn log -r 334814 > > >> --------------------------------------------------------------------= - > > >> --- > > >> r334814 | aharvey | 2014-09-09 04:49:26 +0900 (2014=E5=B9=B409=E6=9C= =8809=E6=97=A5 (=E7=81=AB)) | 2 > > >> lines > > >> > > >> Add documentation for SessionHandler::create_sid(). > > >> > > >> --------------------------------------------------------------------= - > > >> --- > > >> > > >> 334814 aharvey SessionHandler is a > special > > >> class that can be used > > >> 334814 aharvey to expose the current internal PHP session sav= e > > >> handler by inheritance. > > >> 334814 aharvey There are seven methods which wrap the seven > > >> internal session save handler > > >> 334814 aharvey callbacks (open, > > >> close, > > >> 334814 aharvey read, > > >> write, > > >> 334814 aharvey destroy, > > >> gc and > > >> 334814 aharvey create_sid). By defaul= t, > > >> this class will wrap > > >> 334814 aharvey whatever internal save handler is set as > defined by > > >> the > > >> 334814 aharvey > >> linkend=3D"ini.session.save-handler">session.save_handler > > >> 334814 aharvey configuration directive which is usually > > >> files by > > >> 334814 aharvey default. Other internal session save handlers > are > > >> provided by PHP > > >> 334814 aharvey extensions such as SQLite (as > > >> sqlite), Memcache (as > > >> 334814 aharvey memcache), and Memcache= d > > (as > > >> 334814 aharvey memcached). > > >> > > >> I think this should be reverted. > > >> > > > > > > Or it may stay there. > > > It's just a matter of having a copy of create_sid(). > > > I'll add documentation. > > > > > > > I forgot that session_create_id() is needed createSid() method to be mo= re > > useful. > > > > The code for session_create_id() is in the source, but it isn't enabled= . > > I wouldn't like to have different naming session_create_id() and > createSid(). > > > > So I would like to have > > - session_create_id() function > > - createId() function > > because there is > > - session_id() > > since PHP4. > > > > I don't think session internal names do not have to be changed. > > i.e. Macros, etc. > > Any comments? > > > Changing internal or user space API is kind of too late, IMHO. Especially > the user space APIs that are documented. But also the internals, as a lo= t > of extensions are already ported. Also because sessions are a core > functionality where changes should be supported but a good migration path= . > Please target later 7.x versions with this change. But probably would mak= e > sense to create an RFC and start the discussion like already... yesterday= , > so the topic is good discussed and accepted for the next. No problem. I'll write a RFC for this. For the record, please don't document questionable APIs... I'll add comment to source if there are similar cases. Regards, -- Yasuo Ohgaki yohgaki@ohgaki.net --001a114713b8a8b6000519aee711--