Re: Package Proposal: UDDI

From: Date: Mon, 11 Aug 2003 17:33:32 +0000
Subject: Re: Package Proposal: UDDI
References: 1 2  Groups: php.pear.dev 
Request: Send a blank email to pear-dev+get-19519@lists.php.net to get a copy of this message
Hi Greg, > Have you considered using one of the PEAR classes for handling HTTP, > such as HTTP_Request, instead of hard-coding the request in the method? yes, we did. Problem is: We favor the PEAR classes, however the original maintainers of phpUDDI wish that there is always a PEAR-less version of the package available (which is understandable of course). So if we use PEAR classes, we have to use wrapper functions so that "de-PEARifying" the UDDI package is easier. Since we have not done the wrapping yet, we still hard-code the request. But this might very well change in a later release. > You also might find Stephan Schmidt's XML_Util to be very useful in > constructing the xml. For a package as small as this, it would make > sense to just extract the methods you would use. I am aware of Stephan's class, here the same "problems" exist as with HTTP_Request. Synopsis: yes, we will use PEAR classes, but probably in a later stage. > Suggestions: > The documentation is written in an obsolete format, check out > http://www.phpdoc.org/manual.php for details. ok, we will look into that, thanks for the info. > You need to provide a brief description of the problem that this class > (and UDDI) solves, and how the class describes it at the top of the > docs, just grab something from the top of uddi.org and use a @link tag > to reference the full description. sure (we put it into the mail; after acceptance, we will of course include that) > There's no reason for you to extend PEAR, or even reference PEAR, you > don't even use any of the features (bloat) of the class :) correct :) we would like to add PEAR error handling really soon, again we will have to find a way to make un-PEARifying (I make up a lot of new verbs today;) ) easy. But for now one can remove this, correct. > Also, is it GPL? I don't care, but PEAR does :) It should be LGPL, BSD > or PHP license (or something that is equally open-source and > non-restrictive) phpUDDI is GPL, so the package is GPL, as well. I know that this is OSI Approved (http://pear.php.net/manual/en/faq.licenses.php), but we've already raised this issue with the original authors and would prefer the licence to change to LGPL. Best, Christian

« previous php.pear.dev (#19519) next »