Re: PEAR_Server

Tobias Schlitt wrote:

Hi all! I recently read in Greg's weblog [1], that he'll rename his PEAR_Server package to Chiara_PEAR_Server, because of several reasons. Is that really necessary? His former idea of moving the package to PEAR in the future would make much more sense IMHO and would be a great new feature for PEAR. So, let me give some statements to the reasons Greg specified: "Chiara_PEAR_Server will be phasing out use of DB_DataObject in favor of Davey Shafik's Crtx_DB_DataObject, a data access class that uses PDO and is E_STRICT PHP5" I don't believe that this is really necessary. But if it really is, what about moving Crtx_DB_DataObject to DB_DataObjects2?

I don't want to put Crtx_DB_DataObject in PEAR, for one its most likely going to be under an incompatible license and two it may be a commercial product in addition to be under some open source license (thinking GPL)

"Chiara_PEAR_Server depends on Chiara_XML_RPC5" Looks like a PHP5-only version of XML_RPC. What about XML_RPC2 in PEAR?

Someone else took Gregs idea for XML_RPC2 and changed them. Besides there is going to be an xmlrpci extension which will do this :)

"Some PEAR Group members don't like the name, it implies a direct connection to pear.php.net" Currently valid, but if PEAR_Server will be moved to PEAR this becomes invalid.

This isn't the only reason, just the only one he wanted to make public ;) Finally, having Chiara_PEAR_Server on a channel is a testament to the fact that channels work :) Its a working example of channels, cross-channel dependencies and more :) - Davey