Newsgroups: php.internals
Path: news.php.net
Xref: news.php.net php.internals:3110
Mailing-List: contact internals-help@lists.php.net; run by ezmlm
To: Elfyn McBratney <elfyn@cygwin.com>
Cc: internals@lists.php.net
In-Reply-To: <Pine.CYG.4.55.0307012103200.2836@ellixia>
References: <Pine.CYG.4.55.0307012103200.2836@ellixia>
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Message-ID: <1057090143.1360.258.camel@hasele>
Mime-Version: 1.0
Date: 01 Jul 2003 16:09:03 -0400
Subject: Re: [PHP-DEV] Removing SQLite sessions from the default
	distribution
From: sterling@bumblebury.com (Sterling Hughes)

On Tue, 2003-07-01 at 16:08, Elfyn McBratney wrote:
> On Tue, 1 Jul 2003, Sebastian Bergmann wrote:
> 
> > Sterling Hughes wrote:
> > > It offers not one practical advantage.
> >
> >   I though the same, the SQLite euphoria should not be taken too far.
> >
> >   +1 for removing the SQLite Session Save Handled from the default
> >   distribution.
> 
> -1
> 
> Corporate types won't be using this for session management. I guess the majority
> of people that'll "try" this, is the home-grown developers. It's a nice addition
> to session handling; and I feel it's premature to just remove it.
> 
> As Wez said, it's only been in the repo a day. It hasn't matured enough, and
> we're still in the beta stage. Let's wait for feedback and and user flame
> wars until this is removed? :)

But again.  WHY?  Explain to me one case where they are useful?

The short answer is they aren't.  I can write a cURL session handler
that uses HTTP PUT and HTTP GET.  It might even be faster than SQLite
:)  But its not useful.  It provides no practical advantage, so why
should it be there by default?  It shouldn't.  PEAR is the appropriate
place for garbage^M^M^M^Mcode like this.

-Sterling

> 
> Elfyn
> -- 
-- 
"Nothing is particularly hard if you divide it into small jobs." 
    - Henry Ford