I have talked with Giuseppe and he suggested that we might not do TCP Fast Open support for FTP at this time (he argued that FTP is slow either way :).
Instead I might focus on implementing some basics of Metalink protocol for HTTP and FTP resources in Wget. Do you have any thoughts about that? W dniu 28.05.2015 o 00:41, Hubert Tarasiuk pisze: > Hello Wget developers, > > I have prepared TCP Fast Open support for HTTP requests in Wget. > > I have prepared sample TCP segment dump to show how it works: > https://github.com/jy987321/Wget/wiki/TCP-TFO > > The TFO is disabled by default and can be enabled using --tcp-fast-open > option when running Wget. > > The support for TFO has been added only recently to Linux kernel (3.6 > for client and 3.7 for server) and is not supported on Winodws AFAIK. > Therefore, it is added as conditional compilation code. In order to > force the use of it, you can pass --enable-tcp-tfo (--disable-tcp-tfo) > to ./configure script. The default is to include the code if possible > (if required constants are defined in <sys/socket.h>). > > The support for TFO has been added to Python test suite. In order to > make it work, you need to enable both client-side and server-side TFO > support in your Linux kernel: > $ echo 3 > /proc/sys/net/ipv4/tcp_fastopen > > If there is no server-side support, TCP will transparently fall back to > using traditional 3-way handshake. > > Please let me know what do you think of this feature. Suggestions or > comments about patches are more than welcome. > > The code is available as attachment and on Github. > https://github.com/jy987321/Wget/commits/master-hubert > > PS > I was hoping to do some performance tests, but have not found too many > servers that support TFO (actually it is only google.com that I have > found so far). >
signature.asc
Description: OpenPGP digital signature
