I2P_Developers/i2p.www
3
0
Fork 5
Code Issues 27 Pull Requests Actions 1 Packages Projects Releases Wiki Activity

merge of 'c78b41e2bd3d58c4b7c2acfafbf44846a4e60cd9'

Browse Source 
and 'e3db0e6a87a9bdf9505016ef90069beb21cadb69'
This commit is contained in:
str4d
2012-12-06 20:18:24 +00:00
parent de63d02056 86c7468383
commit a517e578da
1 changed files with 22 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

23
www.i2p2/pages/i2cp_spec.html
View File

@ -836,8 +836,14 @@ That message will contain the same nonce sent here.
Later on,
based on the delivery guarantees of the session configuration, the router may
additionally send back another MessageStatusMessage updating the status.
Note: As of release 0.8.1, the router does not send either Message Status Message if
</p><p>
As of release 0.8.1, the router does not send either Message Status Message if
i2cp.messageReliability=none.
</p><p>
Prior to release 0.9.4, a nonce value of 0 was not allowed.
As of release 0.9.4, a nonce value of 0 is allowed, and tells to the router
that it should not send either Message Status Message, i.e. it acts as if
i2cp.messageReliability=none for this message only.
</p>
@ -868,6 +874,21 @@ truncated from 8 bytes to 6 bytes
<p>
As of release 0.7.1.
</p><p>
As soon as the SendMessageExpiresMessage arrives fully intact, the router should return
a MessageStatusMessage stating that it has been accepted for delivery.
That message will contain the same nonce sent here.
Later on,
based on the delivery guarantees of the session configuration, the router may
additionally send back another MessageStatusMessage updating the status.
</p><p>
As of release 0.8.1, the router does not send either Message Status Message if
i2cp.messageReliability=none.
</p><p>
Prior to release 0.9.4, a nonce value of 0 was not allowed.
As of release 0.9.4, a nonce value of 0 is allowed, and tells the router
that it should not send either Message Status Message, i.e. it acts as if
i2cp.messageReliability=none for this message only.
</p><p>
As of release 0.8.4, the upper two bytes of the Date are redefined to contain
flags. The flags must default to all zeros for backward compatibility.
The Date will not encroach on the flags field until the year 10889.