forked from I2P_Developers/i2p.www
defer advanced datagram options to 3.3
This commit is contained in:
@@ -69,9 +69,6 @@ Version 3.2 is not yet implemented, and the changes listed below are preliminary
|
||||
<li>The first line of datagrams sent through port 7655 may have, after the destination,
|
||||
any of the options FROM_PORT=nnnn TO_PORT=nnnn PROTOCOL=nnn
|
||||
<li>RAW RECEIVED now appends to the first line PROTOCOL=nnn to indicate I2P protocol
|
||||
<li>DATAGRAM SEND and RAW SEND now supports options SEND_TAGS=nnn, TAG_THRESHOLD=nnn, EXPIRES=nnnnnnn, and SEND_LEASESET=true|false.
|
||||
These will be passed to I2CP if supported. See <a href="..//i2cp#msg_SendMessageExpire">the I2CP specification</a> for details.
|
||||
Support by the SAM server is optional, it will ignore these options if unsupported.
|
||||
<li>Client and server may now send: PING [arbitrary text] on the control port,
|
||||
with the response:
|
||||
PONG [arbitrary text from the ping], to be used for control socket keepalive.
|
||||
@@ -103,6 +100,9 @@ Version 3.3 is not yet implemented, and the changes listed below are preliminary
|
||||
<li>The same session ID may be used for streams, datagrams, and raw simultaneously.
|
||||
Incoming packets and streams will be routed based on I2P protocol and to-port.
|
||||
<li>STREAM ACCEPT now supports option TO_PORT=nnnn to accept connections on that I2P port only
|
||||
<li>DATAGRAM SEND and RAW SEND now supports options SEND_TAGS=nnn, TAG_THRESHOLD=nnn, EXPIRES=nnnnnnn, and SEND_LEASESET=true|false.
|
||||
These will be passed to I2CP if supported. See <a href="..//i2cp#msg_SendMessageExpire">the I2CP specification</a> for details.
|
||||
Support by the SAM server is optional, it will ignore these options if unsupported.
|
||||
</ul>
|
||||
</p>
|
||||
|
||||
|
Reference in New Issue
Block a user