Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:59171
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.212.42 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <C597222A-C8A2-4A34-AF7D-AE7289B8C825@martins-creations.co.uk>
References: <C597222A-C8A2-4A34-AF7D-AE7289B8C825@martins-creations.co.uk>
Date: Tue, 27 Mar 2012 00:29:35 +0100
Message-ID: <CA+p1Tcb5ktfSYoVfO_hTpi+WW7d7D-zNCGZ1pHCC4_QN-zR9Fg@mail.gmail.com>
To: Martin Amps <php@martins-creations.co.uk>
Cc: PHP internals <internals@lists.php.net>
Content-Type: multipart/alternative; boundary=20cf30780c0853347804bc2dbf24
Subject: Re: [PHP-DEV] SessionHandlerInterface vs Built in Memcache handler
From: arraypad@gmail.com (Arpad Ray)

--20cf30780c0853347804bc2dbf24
Content-Type: text/plain; charset=ISO-8859-1

Hi,

On 26 Mar 2012 17:13, "Martin Amps" <php@martins-creations.co.uk> wrote:
> Is there any notable difference or advantage to either method? The only
thing I can think of is in the code you could fallback to another handler
if a Memcache server was unavailable, or use a slave.

This kind of question should be on the general mailing list not internals.

Whether the flexibility of having that code in userland is worth the
inherent performance penalty is up to you.

Don't forget you can use the SessionHandler class to override particular
parts of the native handler where necessary.

Arpad

--20cf30780c0853347804bc2dbf24--