Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:38541 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 74804 invoked from network); 23 Jun 2008 13:55:28 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 23 Jun 2008 13:55:28 -0000 Authentication-Results: pb1.pair.com header.from=mls@pooteeweet.org; sender-id=unknown Authentication-Results: pb1.pair.com smtp.mail=mls@pooteeweet.org; spf=permerror; sender-id=unknown Received-SPF: error (pb1.pair.com: domain pooteeweet.org from 88.198.8.16 cause and error) X-PHP-List-Original-Sender: mls@pooteeweet.org X-Host-Fingerprint: 88.198.8.16 bigtime.backendmedia.com Linux 2.6 Received: from [88.198.8.16] ([88.198.8.16:54898] helo=bigtime.backendmedia.com) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 4B/DE-23032-E4BAF584 for ; Mon, 23 Jun 2008 09:55:28 -0400 Received: from localhost (unknown [127.0.0.1]) by bigtime.backendmedia.com (Postfix) with ESMTP id A1D52414400E; Mon, 23 Jun 2008 13:57:47 +0000 (UTC) X-Virus-Scanned: amavisd-new at backendmedia.com Received: from bigtime.backendmedia.com ([127.0.0.1]) by localhost (bigtime.backendmedia.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EfR2dbRySNCk; Mon, 23 Jun 2008 15:57:42 +0200 (CEST) Received: from [192.168.10.123] (cust.static.84-253-47-226.cybernet.ch [84.253.47.226]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mls@pooteeweet.org) by bigtime.backendmedia.com (Postfix) with ESMTP id 245854144006; Mon, 23 Jun 2008 15:57:42 +0200 (CEST) Message-ID: <0CA00E5D-CE0E-44F0-81EF-CBC3788F561A@pooteeweet.org> To: Milan Babuskov , PHP Developers Mailing List In-Reply-To: <4E.EC.23032.5BD9F584@pb1.pair.com> Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes Content-Transfer-Encoding: 7bit Mime-Version: 1.0 (Apple Message framework v924) Date: Mon, 23 Jun 2008 15:54:33 +0200 References: <139872287.20070504170744@marcus-boerger.de> <736AED54-1272-4924-A07D-3166A1742A2F@prohost.org> <698DE66518E7CA45812BD18E807866CE2FEF72@us-ex1.zend.net> <463EDD0B.7080300@lsces.co.uk> <4e89b4260705222133y185892bdie46be2e78a2e471b@mail.gmail.com> <4653DA24.8060801@pooteeweet.org> <4e89b4260705230759i64821f14y9bcb7cbcb34aa197@mail.gmail.com> <46546175.5030205@lsces.co.uk> <46546B6C.8010107@pooteeweet.org> <4E.EC.23032.5BD9F584@pb1.pair.com> X-Mailer: Apple Mail (2.924) Subject: Re: [PHP-DEV] [RFC] Starting 5.3 From: mls@pooteeweet.org (Lukas Kahwe Smith) On 23.06.2008, at 14:54, Milan Babuskov wrote: > Lukas Kahwe Smith wrote: >> if nobody with C hacking skills is feeling sufficient pain over >> this, the assumption is that the pool of users is too small or the >> pain is too small. > > sorry for such late reply, but I just joined this group. I'm very > interested in Firebird's future in PHP and I have C skills. However, > to answer your assumption: the pain is too small. > > We have a working 'interbase' extenstion that does all the job, and > does it well. I see that it might get moved to PECL or it might not, > however, it is going to be working for a long time. Current PHP > +Firebird users just don't feel that they need PDO. > > It could be used for new application development, but you'll hardly > find a novice PHP user that is also willing to start hacking into > PHP source code in parallel. Existing users are simply happy with > pure ibase_ functions and ADOdb. > > Now, I don't know about that 'lot of shiny new software' being > written on PDO, and don't really see that Firebird users will care > much. Most of that software is meant to run for ISPs, hosting, etc. > services and Firebird is still not on par with MySQL in that (web > hosting) environment. I use Firebird for everything, except dynamic > online websites where MySQL is simply the best choice. Its not only shiny software, its pretty much all of the standard libs people are developing. So even if you use PHP+Firebird for other stuff you will probably be unhappy that you cannot really use any of the database enabled libs in ezc and ZF. The same will probably be true for PEAR2 etc. > I hope that PDO stuff is not meant to completely replace mysql_, > ibase_, etc. kind of functions in some distant future. It does not seem like its going to happen in the immediate future (aka PHP 6.0) unless we will that we have nobody to contact in case of bugs and more importantly that ensures that we are aware of security issues. So for now it would be sufficient someone steps up and takes over the maintainer role for the ibase extension. This would entail doing the standard maintenance stuff like updating to the new parameter parsing API. It would also entail proactively addressing security issues. Obviously for PHP 6.0 we do need someone to update things for full unicode support eventually as well. regards, Lukas Kahwe Smith mls@pooteeweet.org