of the socket in order to set a bunch of badly documented OS
specific options on it (buffer sizes, etc)
Getting hold of the socket object at listen and connect time is very
valuable
Cheers
Ed W
Chris 'BinGOs' Williams wrote:
On Thu, Jul 16, 2009 at 12:59:09PM +0100, Ed W wrote:
Nick Williams wrote:
Regarding the passing of the socket into clientconnected - I've wished for
this in the past, in order to be able to modify TCP options on the socket,
which didn't seem possible
this into
several protocol streams and feed them to several protocol parsers.
Does that sound like an input filter or is it a wheel because there
might be some state information (several packets to join, etc)
Any thoughts? Any demo apps which show parts of this functionality?
Thanks
Ed W
