Author: adrian.chadd
Date: Sun Jul 5 20:41:27 2009
New Revision: 14134
Added:
wiki/LuscaArchitectureNetworkConnectingToRemoteHosts.wiki
Log:
Created wiki page through web user interface.
Added: wiki/LuscaArchitectureNetworkConnectingToRemoteHosts.wiki
==============================================================================
--- (empty file)
+++ wiki/LuscaArchitectureNetworkConnectingToRemoteHosts.wiki Sun Jul 5
20:41:27 2009
@@ -0,0 +1,12 @@
+#summary How the Squid codebase connects to remote hosts
+
+= Introduction =
+
+There is a set of routines designed to simplify connecting a TCP socket to
a remote host. The API handles the asynchronous socket trickery needed to
complete the connection; checking whether the callback is still valid
before calling it, and handles retrying failed connections.
+
+= Details =
+
+= Shortcomings =
+
+ * Handling the retry is noble. Handling the retry when the opaque
structure being passed in as the "state" anchor is a fildescriptor - not
noble. A whole lot of crap goes on in commResetFD() to create a new
filedescriptor and "dup" the socket state from the previous file descriptor
onto it. This includes the original local IP and port; and -must- therefore
retry the TPROXY related stuff.
+
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"lusca-commit" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/lusca-commit?hl=en
-~----------~----~----~----~------~----~------~--~---
