Re: [PHPLIB-DEV] Incompatible change to active_sessions and auth_user From: Sascha Schumann (sascha <email protected>)
Date: 11/08/99

On Tue, Nov 09, 1999 at 12:19:24AM +0100, Giancarlo Pinerolo wrote:
> > On Sat, Nov 06, 1999 at 05:35:34PM -0600, Adam N. Thompson, MCNE wrote:
> > > If we're talking about incompatible changes anyway, perhaps we should
> > > rip out the support for multiple encoding modes? I don't see this as a
> > > feature, except to support backward compatibility
> >
> > Sometimes it is nice to be able to read the contents of
> > active_sessions without the need to decode it, especially when
> > debugging. But you are right, apart from that I cannot see how
> > multiple encoding modes are usefu
>
>
> Hi guys,
>
> I've came back from a long mental absence from php, phplib and the rest,
> and found that the new 7.2 has finally split start() in session.inc into
> several sub functions. Great!
>
> I proposed this change to make it more easy to control properties deep
> down into extended classes (eg the encoding method) by overriding only a
> part of session.inc. And in fact, as it is now, you can set
>
> $this->that->encode_method="slashes" ;
>
> outside of ct_XXX, in session.inc/set-container(or your extension of it)
>
> I think it's useful to keep unencoded data especially if you (will) want
> to have the capability to adopt another serialization_method (read XML),
> in which case base64 stuff is a bit a nonsense.
>
> I know XML and sharing session data sounds futuristic, but I expect it
> to be more and more an issue

    I agree that PHPLIB should support multiple serialization
    methods. A method should fulfill a special purpose, i.e. it
    can focus on speed, portability, or reduced space usage.

    Limiting PHPLIB to one method means that we will have to find
    a way to choose the correct method. I bet that finding a
    method which fits all requirements will be hard, if not
    impossible. Why do we have data storage containers? They
    exist, because there is no solution which is the best choice
    in all circumstances.

    PHP 4.0's session module allows users to choose between a
    PHP-internal format (high speed) and WDDX (very portable
    format). The latter one is preferred for sharing data between
    applications. So, the future is not that far away. 

-- 

          Regards,

                            Sascha Schumann
                                 Consultant
-
PHPLIB Developers Mailing List. Send messages to <phplib-dev <email protected>>.
To unsubscribe, send "unsubscribe" to <phplib-dev-request <email protected>> in
the body, not the subject, of your message.