c - Set TCP_QUICKACK and TCP_NODELAY -


If you set the TCP_QUICKACK setting on each call on the socket, then TCP_NODELAY is already set, whether QuarkCamp option is set to Will NODELAY overwrite the call?

On connect:

  int i = 1; Setochop (ISKAC, IPPRTOODCDP, TCP_NODELE, (Zero *) and I, Size (I)); On every writing  
  int i = 1;   

Setochop (ISOK, IPPRTOODCPC, TCP_QWarkac, (Zero *) and I, Size (I));

Will TCP_QUICKACK tap be called last call by TCP_NODEL?

There is no direct connection between those two options, they are only for different purposes.

TCP / NADALA is intended to disable / enable buffering of segments so that the data can be sent as a peer as soon as possible, so it is generally used to improve network usage Is done for TCP_QUICKACK is used to accept the delay as soon as possible under some protocol level exchanges, and it is not stable / permanent, subsequent TCP transactions (which are below the robbery This option may be ignored) No actual disagreement between actual protocol level processing or user settings and stack behavior.

Note TCP_NODELAY is portable whereas TCP_QUICKACK is not (works only under 2.4.4+ Linux).

Comments

Popular posts from this blog

mysql - BLOB/TEXT column 'value' used in key specification without a key length -

c# - Using Vici cool Storage with monodroid -

python - referencing a variable in another function? -