HTTP 1.1 keep-alive support in ext/soap/php_http.c ? (fwd)

Re-send to php-general@ since soap@ is a ghost town. Per the msg below, still trying to figure out why each client call to any server results in a new TCP socket being built and closed (BAD!) I finally got around to: print "Request :\n" . $soapClient->__getLastRequestHeaders() . "\n"; print "Request :\n" . $soapClient->__getLastRequest() . "\n"; print "Response:\n" . $soapClient->__getLastResponseHeaders() . "\n"; print "Response:\n" . $soapClient->__getLastResponse() . "\n"; As well as checking tcpdump(8) --- my worst fears are confirmed. The client headers says: Connection: Keep-Alive The server header response says: Response: HTTP/1.1 200 OK Content-Type: application/soap+xml;charset=utf-8 Transfer-Encoding: chunked Date: Tue, 14 Aug 2007 22:35:07 GMT Server: Apache-Coyote/1.1 And yet, the PHP client running from the CLI binary executing the same function call to the server opens & closes two sockets to accomplish the work! ~BAS ---------- Forwarded message ---------- Date: Wed, 8 Aug 2007 11:51:50 -0400 (EDT) From: Brian A. Seklecki <lavalamp@spiritual-machines.org> To: soap@lists.php.net Subject: [SOAP] HTTP 1.1 keep-alive support in ext/soap/php_http.c ? All: Am I correct in reading ext/soap/php_http.c that the SoapClient / SoapServer object will not transmit a "Connection: Close" line into the HTTP header (either via the Client call itself or by modifying Apache's response?) E.g., by default PHP SOAP client recycles HTTP connections to the server for calls to methods using the same server object / instance? l8* -lava (Brian A. Seklecki - Pittsburgh, PA, USA)

	       http://www.spiritual-machines.org/

-- PHP Soap Mailing List (http://www.php.net/) To unsubscribe, visit: http://www.php.net/unsub.php