DXSock Version 6.0


  • Cross Platform (Single Source for Windows, Linux and Mac OS X)



Like Kid Rock Says "They say I'm Cocky... it ain't bragging if ya back it up!"
  • High Performance Socket Suite
  • Over a decade of experience
  • Support for SSL/TLS Encrypted Sockets




Delphi XE Support
  • New Unicode Supported
ARM CPU Support
  • (Embedded Linux Drive Array)
Video and Audio Chat
  • Developed Cross-Platform Chat App
Web Based PDF Generator
  • iPhone App uses us for PDF Output




Nagle


Nagle's algorithm, named after John Nagle, is a means of improving the efficiency of TCP/IP networks by reducing the number of packets that need to be sent over the network.

Nagle's document, Congestion Control in IP/TCP Internetworks (RFC 896) describes what he called the 'small packet problem', where an application repeatedly emits data in small chunks, frequently only 1 byte in size. Since TCP packets have a 40 byte header (20 bytes for TCP, 20 bytes for IPv4), this results in a 41 byte packet for 1 byte of useful information, a huge overhead. This situation often occurs in Telnet sessions, where most keypresses generate a single byte of data which is transmitted immediately. Worse, over slow links, many such packets can be in transit at the same time, potentially leading to congestion collapse.

Nagle's algorithm works by coalescing a number of small outgoing messages, and sending them all at once. Specifically, as long as there is a sent packet for which the sender has received no acknowledgment, the sender should keep buffering its output until it has a full packet's worth of output, so that output can be sent all at once.

Pseudocode


 if there is new data to send
   if the window size >= MSS and available data is >= MSS
     send complete MSS segment now
   else
     if there is unconfirmed data still in the pipe
       enqueue data in the buffer until an acknowledge is received
     else
       send data immediately
     end if
   end if
 end if

Why do we refer to Nagle as a noticeable delay?


Nagle was invented to compensate for networks which were faster than the processing output routines. So instead of sending the word HELLO as potentially 5 packets: H,E,L,L,O. An algorithm was invented to assure these 5 characters would be collected into a single packet if presented fast enough. In today's world, Nagle is not really useful unless you have really poor networking environments.

Our product defaults to Nagle enabled as we have to assume you do not know what you are doing, and we assume you have not read our online documentation.

Related Keyword:


October 16, 2010
Testing
width 0 cellspacing 0 cellpadding 0 CELL 1 Description of a product image images Thumb SN850940...
September 01, 2010
Recent Questions
Recent Questions Do you still include the source like in the past Yes We include full source code...
August 20, 2010
Revisions Towards Final Release
Revisions Towards Final Release AUGUST 2010 Our multi language resource files have been expanded...
August 18, 2010
Demonstrations
Demonstrations Below is a constantly growing list of demonstrations We are currently developing...
August 14, 2010
Early Release Orders
Early Release Orders Please be sure you have read view June 2010 Release June 2010 Release as this...




Popularity: 1.07% [?]