Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:46158
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
Received-SPF: pass (pb1.pair.com: domain gmail.com designates 209.85.222.176 as permitted sender)
DomainKey-Status: bad
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        b=mZQL8ngy+/42fTyoaATV0Z6ImpOqXk/qGVNQzTceGJP5LGeFp5up+3pui9DpL2UYDe
         UN4edkxWfTj8NVmE4f9txkhYKOrJKSRhVvNjiMAnrbP9lbjobIMqqhOErlM8ObAjSE8E
         ktdCkdeyncl4jJuoJZLbioQ15CAC/2yVrb+DU=
MIME-Version: 1.0
In-Reply-To: <d4b907690911212116m6c122505qc2bf7a4d56bd25de@mail.gmail.com>
References: <d4b907690911212116m6c122505qc2bf7a4d56bd25de@mail.gmail.com>
Date: Sat, 21 Nov 2009 21:20:26 -0800
Message-ID: <bd9320b30911212120w4ab31841xb87bb876ce4e8015@mail.gmail.com>
To: Arpad Ray <arraypad@googlemail.com>
Cc: internals@lists.php.net
Content-Type: text/plain; charset=UTF-8
Subject: Re: [PHP-DEV] [PATCH] default session serialization
From: mike503@gmail.com (Michael Shadle)

On Sat, Nov 21, 2009 at 9:16 PM, Arpad Ray <arraypad@googlemail.com> wrote:

> However it would be a significant BC break, as old serialized session
> records would be unreadable after upgrading. We could mitigate this by
> providing a script to convert old session files.

I would say just a note saying "old session files if they exist will
be unreadable after this change"

Also GC would not clean them up either? That might be the worse thing.
Upgrading should be something people understand could mean downtime or
slight changes like losing session data and it should be an acceptable
loss... I use MySQL for my sessions currently; would the key for the
session be changed then or only the session data? If so, only people
using files would be affected anyway, right?