#33765 [Opn->Asn]: SOAP one-way is not fire-and-forget
| From: | sniper@php.net | Date: | Tue, 19 Jul 2005 08:44:23 +0000 |
| Subject: | #33765 [Opn->Asn]: SOAP one-way is not fire-and-forget | ||
| References: | 1 | Groups: | php.bugs |
| Request: | Send a blank email to php-bugs+get-82127@lists.php.net to get a copy of this message | ||
ID: 33765
Updated by: sniper@php.net
Reported By: php at sowen dot de
-Status: Open
+Status: Assigned
Bug Type: SOAP related
Operating System: Gentoo Linux
PHP Version: 5.1.0b3
-Assigned To:
+Assigned To: dmitry
Previous Comments:
------------------------------------------------------------------------
[2005-07-19 09:20:37] php at sowen dot de
Description:
------------
When I try to make a SOAP call to a server that doesn't reply with an
answer, my client keeps on waiting until the server finished it's work.
Shouldn't one-way operation be "fire-and-forget" in order to make more
sense?
This could be solved by returning a HTTP 200 response and closing the
socket, right after the SOAP call was received by the server.
Reproduce code:
---------------
Server code:
------------
public function onewaytest() {
sleep(50);
}
Client code:
------------
$soap = new SoapClient(null, '...');
$starttime=time();
$soap->onewaytest();
echo time()-$starttime." sec\n";
Expected result:
----------------
Just the network time-overhead caused by HTTP connect and POST.
Actual result:
--------------
Above 50 sec.
------------------------------------------------------------------------
--
Edit this bug report at http://bugs.php.net/?id=33765&edit=1