status-im
/
tcp-shaker
mirror of https://github.com/status-im/tcp-shaker.git
2
0
Fork 0
Code Issues Projects Releases Wiki Activity

Add description about the maturity

This commit is contained in:
Tevin Zhang 2019-11-12 18:45:05 +08:00
parent 2b1e77e59f
commit 00eab0aefc
No known key found for this signature in database
GPG Key ID: EE7DA2A50F0960FB
1 changed files with 3 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

3
README.md
View File

@ -12,6 +12,8 @@ HAProxy does this exactly the same, which is:
2. SYN-ACK 2. SYN-ACK
3. RST 3. RST
This implementation has been running on tens of thousands of production servers for years.
## Why do I have to do this ## Why do I have to do this
In most cases when you establish a TCP connection(e.g. via `net.Dial`), these are the first three packets between the client and server([TCP three-way handshake][tcp-handshake]): In most cases when you establish a TCP connection(e.g. via `net.Dial`), these are the first three packets between the client and server([TCP three-way handshake][tcp-handshake]):
@ -45,6 +47,7 @@ considered as some misbehavior of client.**
- Linux 2.4 or newer - Linux 2.4 or newer
There is a **fake implementation** for **non-Linux** platform which is equivalent to: There is a **fake implementation** for **non-Linux** platform which is equivalent to:
```go ```go
conn, err := net.DialTimeout("tcp", addr, timeout) conn, err := net.DialTimeout("tcp", addr, timeout)
conn.Close() conn.Close()