RE: [PEAR-DEV] SOAP interop server on pear.php.net

> >> Why should this be done on pear.php.net? If we now start to > >> provide demo setups on pear.php.net for certain packages, > >> others will follow and we'll soon run into technical problems. > > > >It's easier to set it up on pair1 right now, but we might as well use > >pair2 (that box only has 128MB of memory though). > > Are you sure that we want this? I have nothing against allowing > Shane to put up a SOAP demo on pair1 in particular, but I'm afraid > that other people will also claim to get demo space in the > future - I'm actually not sure if this is a wise thing to do. > I think SOAP should be the exception in this case. One only has to look at the interop link that Shane posted and it becomes pretty obvious that the SOAP class is (a) in good company, and (b) damn impressive. The interop server on pear.php.net is not there for demo purposes, but it's there as a base to test interoperability with other SOAP implentations. I checked out the results page and Shane's SOAP classes do a pretty damn fine job. So the short answer is that if people want a 'demo space' for their code on pear.php.net then they should be out of luck. Shane's SOAP classes are of a scale far exceeding a class then needs 'demo space' plus any old-timers on the list (me included) will know Shane's contribution to PHP way back on the v2/early v3 days and to be quite frank I think he deserves it. Plus, I think his SOAP class needs more attention. This is going to start a whole other thread, but considering the scarcity of really fine SOAP implementations in PEAR (I cannot speak for the xmlrpc-epi SOAP additions), I think that this class is actually worth supporting. I don't mean "yes you can put in PEAR" support but more that the SOAP classes should become a PEAR 'officially cool' class in a way the the DB classes are. People interested in seeing PEAR become more acecepted and used should be on the lookout for potential flagship classes such as this. Bickering about editor format definitions is not going to do anything for PEAR evangelism but something like this an integral part of PEAR is. Now before we all go hollering on about this, I think there is a precedent for this sort of thing. I'm not aware of the politics or policy around this so I'm quote happy to be proved wrong. Observant types will notice the presence of smarty.php.net. Can it be that PHP has accepted Smarty as the 'officially cool' template language of PHP? If that is the case then why not SOAP being an 'officially cool' part of PEAR? Cheers, Graeme