Re: [PDO] [RFC] An Idea for PDO 2

[email protected] (Lukas Kahwe Smith)
Newsgroups php.pdo
Message-ID <[email protected]>
On 14.02.2008, at 02:49, Christopher Jones wrote:

>
>
> Andi Gutmans wrote:
> > - JDBC like solution - Spec only as a set of interfaces/contracts  
> (also
> > under some collaboration agreement although there may be an option  
> not
> > to have that); drivers are fully implemented by the vendors; there  
> is no
> > PDO core in this option. I didn't like this for three reasons; we  
> lose
> > the advantage of having shared infrastructure for the various  
> drivers
> > which ultimately may make it harder to make fixes and/or  
> improvements
> > propagate to the various drivers, it may encourage less sharing of
> > knowledge between the vendors, and we would need to deal with symbol
> > namespacing issues to make sure the different drivers don't clash at
> > runtime.
>
> We'd support this. From my last set discussions internally, we'd need
> the spec to be under CLA.

Ok, thats a problem. I do not see much of a chance to convince anyone  
on php.net to do this. But lets say its not under a CLA, how is this  
different than you guys using the ZE2 API? Is it just because Oracle  
considers anything closer to RDBMS to be more of a risk? If we say  
that we do not expect much direct collaboration at all from any of the  
concerned vendors, is that still an issue?

> From my point of view, the interesting crux of the PDO discussions is
> that the development and release _process_ is the key factor in
> determining what risk (and hence need for CLA's and licenses) exists.

Right. The base line is that anyone can setup a PEAR channel and  
distribute PHP or C code on their own infrastructure. We are looking  
if there is a way to more closely integrate you guys into the php.net  
infrastructure.

regards,
Lukas
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.