W3C home > Mailing lists > Public > www-lib@w3.org > January to March 2004

RE: Closing connections

From: Goldberg, Anton <antong@amazon.com>
Date: Mon, 8 Mar 2004 10:14:36 -0800
Message-ID: <F994257049853A4C8153385C72E18C08025E4275@ex-mail-sea-01.ant.amazon.com>
To: "Andi Reinbrech" <AReinbre@multichoice.co.za>, <www-lib@w3.org>
Add the Connection:close header. By default libwww sends Connection:Keep-Alive.
	-----Original Message-----
	From: www-lib-request@w3.org [mailto:www-lib-request@w3.org] On Behalf Of Andi Reinbrech
	Sent: Monday, March 08, 2004 2:18 AM
	To: www-lib@w3.org
	Subject: Closing connections
	Hi, I hope someone still reads these posts, I am stuck in a bit of a mess.
	I need to send a string via POST to a .dll on the client, then receive a string back and parse it.
	For some reason, M$ IIS closes any ports after streaming data *EXCEPT* after a POST to a Web Service DLL.  The connection lingers and waits for libwww to time out (which is much too long for me to wait, as the response has been sent back already).
	Java handled this OK, but JNI turned out to be way too slow, hence the C attempt.
	I think Java looked at the Content-length header, and if the body content length matched it would assume that the transaction is done.
	Any ideas?
	Everything in this e-mail and attachments relating to the official business of MultiChoice Africa is proprietary to the company. Any view or opinion expressed in this message may be the view of the individual and should not automatically be ascribed to the company.  If you are not the intended recipient, you may not peruse, use, disseminate, distribute or copy this message. If you have received this message in error, please notify the sender immediately by email, facsimile or telephone and destroy the original message.
Received on Monday, 8 March 2004 13:16:03 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:33:56 UTC