Re: [SOAP] General question

From: Date: Tue, 05 Aug 2003 14:49:34 +0000
Subject: Re: [SOAP] General question
References: 1 2 3 4 5  Groups: php.soap 
Request: Send a blank email to php-soap+get-924@lists.php.net to get a copy of this message
Abdul-wahid Paterson wrote:
I don't know the status of PECL::SOAP, Shane should be able to tell us more. Some improvements in PEAR::SOAP are planned with the coming of PHP5.
It would be nice to have a Road map somewhere so that a proposed schedule can be seen. I first tried the PECL version when trying to write my .NET client and at first I was impressed by the way it worked but alas, after testing on some simple test sites when I tried it with the service I really wanted to consume I got: FATAL: emalloc(): Unable to allocate -137289284 bytes Obviously some sort of memory allocation in the PECL code that probably wouldn't be too hard to track down. I then tried PEAR:SOAP but did not have much more luck. I just seemed to get loads of errors e.g. Warning: current(): Passed variable is not an array or object in /usr/lib/php/SOAP/WSDL.php on line 378
Hmmm ... since that email, I have PEAR:SOAP running just fine (as a client). I still don't like the API, and it seems a little slow, but it works.
Eventually, after a few days of trying out various ideas to get the thing working I gave in and wrote it in Perl instead which only took a couple of hours. (I will need to recode it in PHP at some point). Anyway, my point is, it seems that for a new user of SOAP in PHP there are not many pointers as to the current state of development, whether one should use PECL or PEAR::SOAP and a Road Map somewhere would be helpful. Perhaps some collaborative online documentation somewhere with more examples, an FAQ etc would be helpful. What about a Wiki or something similar?
I agree. I'm pretty deep in SOAP-land now. I'm hoping to get more involved in PECL:SOAP development once I'm done with my current project. -- Bill Moran Potential Technologies http://www.potentialtech.com

« previous php.soap (#924) next »