Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:3116 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 69977 invoked from network); 1 Jul 2003 20:45:40 -0000 Received: from unknown (HELO bm5.mail.tds.net) (216.170.230.85) by pb1.pair.com with SMTP; 1 Jul 2003 20:45:40 -0000 Received: from halcyon.workpc.tds.net ([204.246.8.151]) by bm5.mail.tds.net with ESMTP id <20030701204540.BLMG11201.bm5@halcyon.workpc.tds.net>; Tue, 1 Jul 2003 15:45:40 -0500 To: Sterling Hughes Cc: internals@lists.php.net, Sascha Schumann , Wez Furlong In-Reply-To: <1057087738.1360.216.camel@hasele> References: <1057087738.1360.216.camel@hasele> Content-Type: text/plain Organization: Message-ID: <1057092339.6996.19.camel@halcyon.workpc.tds.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 01 Jul 2003 15:45:40 -0500 Content-Transfer-Encoding: 7bit Subject: Re: [PHP-DEV] Removing SQLite sessions from the default distribution From: jason@php.net (Jason Greene) > Is not a hard cross to bear, and considering that sqlite enabled > sessions should be avoided in the first place, I think its a bad idea to > include them by default. > > -Sterling + 1 One thing I would like to point out here, is that a session backend is transparent to the user. As long as their sessions are stored, and the api works, they really don't care. So why would we want to use a different embedded technology? The only logical reasons are: it offers more functionality, or it is better performing. I still can not see a functionality difference. As to performance, I think it is obvious that file based sessions are faster. -Jason -- Jason Greene