Hi Arnaud,
The client is on one server, the server is on another. Both are Linux. They are accessing each other over the internet. There is only the Client that is accessing the eb service now. The network guy told me that the network is optimal.
The internet being what it is you can hardly guarantee anything that goes over it. A network congestion or any other event which can happen will affect performance.
There is not much program logic being coded in the Server now. So it does is generate a random number, log it in a log file together with some other variables.
Could it possibly be PEAR SOAP not connecting to the server in a optimal way?
Are you using SSL ? SSL will slow things down (note i'm not saying don't use SSL because it's slow, i'm just pointing out that using SSL slows things down).
Try and connect using command-line curl to the web service.
What i did once what to write the payload to a file and using curl options to connect to the web service and see the answer i got and in how much time.
Something like
curl --trace-ascii trace -3 -v -H "Content-Type: text/xml; charset=UTF-8" -H "SOAPAction: \"\"" -d @content.xml https://path/to/webservice
content.xml contains the xml enveloppe the webservice is expecting.
You can see how it works with that. Using a for loop you can check how many queries you can send.
Arnaud.
Regards, Tan Ai Leen PS:Thanks for such prompt reply.
-- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php
