[Mono-devel-list] HttpSoapWebServiceHandler.SerializeResponse closes the HttpResponse
Konstantin Triger
kostat at mainsoft.com
Mon Jun 6 04:10:58 EDT 2005
Hi,
I don't think it's the case here: server already successfully accepted
and understood the message. So it definitely was "complete". Now it
sends the response back and after that closes the connection. But it
seems more correct to call Flush only.
Regards,
Konstantin Triger
Gonzalo Paniagua Javier wrote:
>On Sun, 2005-06-05 at 20:30 +0300, Konstantin Triger wrote:
>
>
>>How closing the connection may help when only a part of the data arrived?
>>
>>Regards,
>>Konstantin Triger
>>
>>
>>
>>Gonzalo Paniagua Javier wrote:
>>
>>
>>
>>>On Sun, 2005-06-05 at 17:12 +0300, Konstantin Triger wrote:
>>>
>>>
>>>
>>>
>>>>Hi Lluis,
>>>>
>>>>The HttpSoapWebServiceHandler.SerializeResponse currently closes the
>>>>response when finished. What makes the "keep-alive" to not work and
>>>>actually a new socket is opened for each request.
>>>>
>>>>Is this done on purpose?
>>>>
>>>>
>>>>
>>>>
>>>I recall something related to a POST being sent with no Content-Length
>>>or 'chunked' encoding being the cause of not reusing the connection.
>>>
>>>
>
>If the server does not know the length and you're not sending it
>'chunked', the server cannot reuse the connection.
>
>ServicePoint takes care of reusing the connection when possible and
>closing the HttpResponse does not mean that the socket will be closed
>right away unless we realize the server did close it.
>
>-Gonzalo
>
>
>_______________________________________________
>Mono-devel-list mailing list
>Mono-devel-list at lists.ximian.com
>http://lists.ximian.com/mailman/listinfo/mono-devel-list
>
>
More information about the Mono-devel-list
mailing list