Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:56749 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 25238 invoked from network); 4 Dec 2011 09:55:58 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 4 Dec 2011 09:55:58 -0000 Authentication-Results: pb1.pair.com smtp.mail=smalyshev@sugarcrm.com; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=smalyshev@sugarcrm.com; sender-id=pass Received-SPF: pass (pb1.pair.com: domain sugarcrm.com designates 67.192.241.143 as permitted sender) X-PHP-List-Original-Sender: smalyshev@sugarcrm.com X-Host-Fingerprint: 67.192.241.143 smtp143.dfw.emailsrvr.com Linux 2.6 Received: from [67.192.241.143] ([67.192.241.143:46535] helo=smtp143.dfw.emailsrvr.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4A/32-13454-DA34BDE4 for ; Sun, 04 Dec 2011 04:55:58 -0500 Received: from localhost (localhost.localdomain [127.0.0.1]) by smtp4.relay.dfw1a.emailsrvr.com (SMTP Server) with ESMTP id 6E9BA3A056F; Sun, 4 Dec 2011 04:55:55 -0500 (EST) X-Virus-Scanned: OK Received: by smtp4.relay.dfw1a.emailsrvr.com (Authenticated sender: smalyshev-AT-sugarcrm.com) with ESMTPSA id 3004E3A055F; Sun, 4 Dec 2011 04:55:55 -0500 (EST) Message-ID: <4EDB43AA.7080105@sugarcrm.com> Date: Sun, 04 Dec 2011 01:55:54 -0800 Organization: SugarCRM User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.6; rv:8.0) Gecko/20111105 Thunderbird/8.0 MIME-Version: 1.0 To: Yasuo Ohgaki CC: "internals@lists.php.net" References: <4EBDC283.3040700@yahoo.co.jp> <4ED727FB.7030001@uw.no> <4EDA9788.5070901@sugarcrm.com> <4EDAEB9A.3050105@sugarcrm.com> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Strict session? From: smalyshev@sugarcrm.com (Stas Malyshev) Hi! > Since it is just adding new separate structure to session module, but > PHP itself checks API version number. So users cannot use the same > binary module anyway. I should have said API, not ABI. > > Now it should compile with msession which uses PHP_MOD_SID/PS_MOD_FUNCS_SID. That's the problem. All versions in 5.3.x and 5.4.x lines should be binary compatible, means no changes that aren't binary compatible can go into 5.3 or 5.4. -- Stanislav Malyshev, Software Architect SugarCRM: http://www.sugarcrm.com/ (408)454-6900 ext. 227