Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:81027 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 58676 invoked from network); 23 Jan 2015 06:47:25 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jan 2015 06:47:25 -0000 Authentication-Results: pb1.pair.com header.from=smalyshev@gmail.com; sender-id=pass Authentication-Results: pb1.pair.com smtp.mail=smalyshev@gmail.com; spf=pass; sender-id=pass Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.192.182 as permitted sender) X-PHP-List-Original-Sender: smalyshev@gmail.com X-Host-Fingerprint: 209.85.192.182 mail-pd0-f182.google.com Received: from [209.85.192.182] ([209.85.192.182:65370] helo=mail-pd0-f182.google.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 9F/33-61273-D7EE1C45 for ; Fri, 23 Jan 2015 01:47:25 -0500 Received: by mail-pd0-f182.google.com with SMTP id z10so4395458pdj.13 for ; Thu, 22 Jan 2015 22:47:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=/N67rwOJeMFEm5s5IhIRRsWkxJvSKhe8x+dX8L03a2g=; b=q6v5xWN47K7zb/v8eyUrXNwFz6XAP5gg2mYOOhIpdVYDCZhHlmSSMOSUnzztu0pXgw qifgL0SVeK03K0nsVEKq2X6KX7g7HDsANchifmErrYd+WTHk6Nd1MritnZpqN3oxg+b2 uxzPCwKriMCOW7vaeWSHG9iiUdKLqcPLoQH6NtuY3XBhqi5723xbMUBMdmtlwoVUYhbD P7gEw3jXi84NIBKqreGsmv52Nopx/ehWz+mU+8XfWginfxs5li3PkBnfWE5hjSSskFmi aa4B+CTw9nvm43V/EQkwBryPz48GQcSqrc+pcxHrRaYvdveVsCIshJwwlgLorpfbYtlj e5SQ== X-Received: by 10.68.136.7 with SMTP id pw7mr8541853pbb.168.1421995641588; Thu, 22 Jan 2015 22:47:21 -0800 (PST) Received: from Stas-Air.local (108-66-6-48.lightspeed.sntcca.sbcglobal.net. [108.66.6.48]) by mx.google.com with ESMTPSA id ds16sm767121pdb.65.2015.01.22.22.47.20 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 22 Jan 2015 22:47:20 -0800 (PST) Message-ID: <54C1EE77.7040000@gmail.com> Date: Thu, 22 Jan 2015 22:47:19 -0800 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: Yasuo Ohgaki CC: "internals@lists.php.net" References: <54C1D562.1080402@gmail.com> In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Removing base class from session handler From: smalyshev@gmail.com (Stanislav Malyshev) Hi! > User may extend SessionHandler class like > > class MySession extends SessionHandler {} > > but user cannot extend base class(SessionHandler) capability because > user script > cannot access to PS(mod_data). Not sure what you mean by that. Absence of access to PS(mod_data) certainly doesn't mean the user can not extend it's function, e.g. the manual demonstrates EncryptedSessionHandler - is there something wrong with that? Of course, there can be many more examples of it. > I should have written "remove the SessionHandler class". As I wrote, > user may > extend SessionHandler class. I don't think this is a good idea. There are valid uses of this, and there's code using it. Removing it does not achieve any goal as far as I can see. > However, defining user session class as > class MySession extends SessionHandler {} > have no merit. Users must implement required methods to be useful. I'm not sure why you say that - if they don't implement any methods, wouldn't that class work exactly as the native handler? Isn't the native handler useful? -- Stas Malyshev smalyshev@gmail.com