[Zope-dev] Zope closes connection if the client closes the write-end of connection

Tres Seaver tseaver at palladion.com
Fri Oct 16 11:00:59 EDT 2009


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Leonardo Rochael Almeida wrote:
> On Fri, Oct 16, 2009 at 16:36, Tres Seaver <tseaver at palladion.com> wrote:
>> [...]
>> You might also look at "fixing" varnish:  I don't know of any valid
>> reason for it to be using the "half-open" connection model to test that
>> an HTTP-based backend is "up"
> 
> Going out on a limb here, but I think Varnish might be trying to save
> on file-descriptors. It could be a while before a backend-server
> answers and Varnish could have a large number of fds open on any given
> time while talking to both clients and servers.

Hmmm?  A TCP socket corrresponds to exactly one open file descriptor,
which has to stick around for the response data to come back on.
"Half-closing" it is just silly, and is only guaranteed to work where
both ends expect to handle this case.  Given HTTP's request-response
model, it makes very little sense at all for the client to preemptively
shutdown writes on the connection.


Tres.
- --
===================================================================
Tres Seaver          +1 540-429-0999          tseaver at palladion.com
Palladion Software   "Excellence by Design"    http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrYiqsACgkQ+gerLs4ltQ5dSgCgnqousqxHj8mGUIAZN2P9JTrZ
AeMAn01dRMSOYtRm4usudDBN3IZ4m9ii
=avfS
-----END PGP SIGNATURE-----



More information about the Zope-Dev mailing list