ndt-dev - [ndt-dev] [ndt] r446 committed - Restructured sentence about timeout limit.
Subject: NDT-DEV email list created
List archive
- From:
- To:
- Subject: [ndt-dev] [ndt] r446 committed - Restructured sentence about timeout limit.
- Date: Thu, 04 Aug 2011 09:46:21 +0000
Revision: 446
Author:
Date: Thu Aug 4 02:45:25 2011
Log: Restructured sentence about timeout limit.
http://code.google.com/p/ndt/source/detail?r=446
Modified:
/wiki/NDTProtocol.wiki
=======================================
--- /wiki/NDTProtocol.wiki Thu Aug 4 02:22:07 2011
+++ /wiki/NDTProtocol.wiki Thu Aug 4 02:45:25 2011
@@ -78,7 +78,7 @@
The type of each NDTP-Control message can be found after reading the first octet. The length of each NDTP-Control message can be computed upon reading its fixed-size part. No message is shorter than 3 octets.
-An implementation SHOULD expunge unused state to prevent denial-of-service attacks, or unbounded memory usage, on the server. For example, if the full control message is not received within some number of minutes after it is expected, the TCP connection associated with the NDTP-Control session SHOULD be dropped. In absence of other considerations, 10 minutes seems like a reasonable upper bound.
+An implementation SHOULD expunge unused state to prevent denial-of-service attacks, or unbounded memory usage, on the server. For example, if the full control message is not received within some number of seconds after it is expected, the TCP connection associated with the NDTP-Control session SHOULD be dropped. NDTP does not define any timeout limit.
=== Message structure ===
- [ndt-dev] [ndt] r446 committed - Restructured sentence about timeout limit., ndt, 08/04/2011
Archive powered by MHonArc 2.6.16.