docs: Added disclaimer about fragmented channels lack of ack resend l…

…imiting
MidLevel · Dec 12, 2019 · 139a0b5 · 139a0b5
1 parent f2567f1
commit 139a0b5
Showing 1 changed file with 4 additions and 1 deletion.
diff --git 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``.
+* 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.