# SessionHandlerInterface vs Built in Memcache handler

- Thread: https://externals.io/message/59166
- Original archive: https://news-web.php.net/php.internals/59166
- Started by Martin Amps on 2012-03-26T16:13:04+00:00
- Messages: 2
- Reply by email to internals@lists.php.net
- More for agents: search with https://externals.io/search.md?q={query} · JSON API at https://externals.io/api · documentation at https://externals.io/llms.txt

---

## #59166 — Martin Amps — 2012-03-26T16:13:04+00:00

URL: https://externals.io/message/59166#59166

Hi Internals,

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.

Regards,

Martin

---

## #59171 — Arpad Ray — 2012-03-26T23:29:35+00:00

URL: https://externals.io/message/59166#59171 · In reply to: #59166

Hi,


> 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