From 139a0b5d8c7b2e07b9ec9738b046a5d68c638976 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Albin=20Cor=C3=A9n?= <twoten@twoten.io> Date: Thu, 12 Dec 2019 16:44:36 +0100 Subject: [PATCH] docs: Added disclaimer about fragmented channels lack of ack resend limiting --- README.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index 5fe771b..41f2904 100644 --- a/README.md +++ b/README.md @@ -119,4 +119,7 @@ Ruffles is designed to be mostly lockless. There are however a few situations wh * If the user sends a packet that is due for merging and Ruffles is trying to flush the merged packets. This can be avoided by sending with ``noDelay = true``. * If the user sends two packets that is due for merging at the same time. This can be avoided by sending with ``noDelay = true``. * If the user calls ConnectNow and Ruffles is modifying connections (Disconnecting, Connecting or Timing out). This can be avoided by using ``ConnectLater``. -* If the user calls DisconnectNow and Ruffles is modifying connections (Disconnecting, Connecting or Timing out). This can be avoided by using ``DisconnectLater``. \ No newline at end of file +* If the user calls DisconnectNow and Ruffles is modifying connections (Disconnecting, Connecting or Timing out). This can be avoided by using ``DisconnectLater``. + +## Fragmented +The fragmented channel currently does not have any flow rate for ack resends. \ No newline at end of file