Re: [PHP-SOAP-DEV] [PHP-DEV] [NEW-EXTENSION]ext/soap : first play around ...

[brad l. <rod...@ya...>]

--- phpsurf <ph...@if...> wrote:
> Hi !
> 
> I just started to play with your new extension as soon as I saw your mail
> this morning on PHP-DEV !
> 
> It's really a good job and I am very impatient to play with the final
> release ...
> 
> here are a few suggestions/bugs/requests to help you make this ext really
> great :
> 
> - nice to have : a proxy set up for soap requests
> something like :
> 
> $client = new SoapObject("uri", "urn");
> $client->setProxy("proxyUri", 8080);

what is the uri for in the soap constructor for?...
currently the first parameter is the uri of the proxy.

$client = new SoapObject("http://proxy.endpoint.com:8080/test.php",
"urn:test");
that is the use without wsdls...
or
$client = new SoapObject("http://proxy.endpoint.com:8080/test.wsdl");
then the wsdl will have to define the endpoint



> ...
> 
> - bug : but this bug way come from PHP and not from the ext ...
> this deals with case-sensitivity of function names !
> this reminds me a quite long thread on PHP-DEV about that a few weeks ago !
> :)
> 
> $myObject = new
> SoapObject("http://www.localhost.com/PhpSoapToolkit/samples/object-server-sr
> c.php", "urn:Object");
> echo $myObject->getData();
> 
> the method name getData is used to write the XML request ...
> but as function names are not case sensitive, this gives the following XML
> tag :
> <getdata xmlns="urn:Object" ...
> 
> and then this doesn't work when you try to call a SOAP server that is not
> writen in PHP !
> because in SOAP, method names are case-sensitive !

 Yeah i understand the problems with this.... I'm not sure how this would work
seeing that when you use a WSDL this is taken care of.

$soapobject = new SoapObject("http://www.server.com/server.wsdl");
$soapobject->getData();

if the wsdl defines the getData method in uppercase then it will send
<getData .... instead of <getdata ....

Most soap implementations use wsdl's now-a-days.

But i will keep that in mind.

> 
> - important feature : the ability to pass named parameters ...
> insteed of having parameters called param0, param1, param2, ... it would be
> very usefull to have the ability to specify the name of the parameter.
> once again, this would allow to be SOAP-compliant with other systems not
> running PHP.

 Again when using wsdl's it will use the name of the parameter that the wsdl
supplies it. If this is a huge consern that the server you are talking to
doesn't use wsdls and needs named parameters. give me the implementation and
specfics and ill look into it further.


I tried to make the client code clean as possible with out stuff like
$soap->call_method("getData");
and
$soap->set_param_name("data");

it is soo much cleaner to read
$soap->getData();

and the functionality is there when using wsdls. 

> 
> that's all for the moment :)
> 
> once again, good job !
> 

 thanks for the feedback....

Let me know if you still have a consern about the above issues if the wsdl
support does do what you will need.


 _brad_


__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com