On Tue, Mar 25, 2014 at 1:55 PM, Andrey Andreev <[email protected]> wrote:
> Hi,
>
> In order to avoid further arguments about whether a separate function
> for read-and-close is better or not, I've added an alternative
> proposal - to rename the option to 'read_close' or 'read_and_close'.
> After all, the most important thing is that it's not 'read_only'.
I agree "read_and_close" is much better discribing what it really does , so
I prefer it.
For non BC changes etc.. , please, consider that you'll have a big time for
rethinking the whole session module for PHP6 if you want to (and I think
I'll be part of deep discussions here)
So don't bother too much in searching solutions for introducting new
concepts in PHP5.X session module while keeping BC. Keep all those for PHP6.
We are near 5.6 freeze, not that I dont want new shinny features, but what
I want for 5.6 is something both consistent and voted, should it be "just a
tiny feature".
Work and thoughts are not lost anyway.
Julien.P