Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:71574 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 16466 invoked from network); 26 Jan 2014 00:44:17 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 26 Jan 2014 00:44:17 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.203 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.203 smtp203.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.203] ([67.192.241.203:58758] helo=smtp203.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 55/95-19300-06A54E25 for ; Sat, 25 Jan 2014 19:44:17 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp10.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 746031B8215; Sat, 25 Jan 2014 19:44:14 -0500 (EST) X-Virus-Scanned: OK Received: by smtp10.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 0B24B1B8039; Sat, 25 Jan 2014 19:44:13 -0500 (EST) Message-ID: <52E45A5D.7020807@sugarcrm.com> Date: Sat, 25 Jan 2014 16:44:13 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: Yasuo Ohgaki CC: Andrey Andreev , PHP Internals References: <52E319F2.8080705@sugarcrm.com> <52E3959D.4000103@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Session IP address matching From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > I have client who want to distinguish session by session ID. > They don't want to store IP in session name. > They would like to know creation and modification time w/o > actually reading session data for performance reasons. That would probably require custom read/write methods. > which is really bad thing to do. session_create_id() generate ID using > the same code PHP generates ID which is much secure than above and > supposed to be faster than user land script. I agree that exposing the ID creation function is a good addition (actually if it was available I'd probably use it in other contexts where I need a random token, not necessarily a session ID as such). Maybe we need even more generic function and have session reuse that code, too. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227