diff --git a/i2p2www/pages/site/docs/api/samv3.html b/i2p2www/pages/site/docs/api/samv3.html index deede231..2059dd3f 100644 --- a/i2p2www/pages/site/docs/api/samv3.html +++ b/i2p2www/pages/site/docs/api/samv3.html @@ -69,9 +69,6 @@ Version 3.2 is not yet implemented, and the changes listed below are preliminary
  • 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
  • RAW RECEIVED now appends to the first line PROTOCOL=nnn to indicate I2P protocol -
  • 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 the I2CP specification for details. - Support by the SAM server is optional, it will ignore these options if unsupported.
  • 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
  • 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.
  • STREAM ACCEPT now supports option TO_PORT=nnnn to accept connections on that I2P port only +
  • 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 the I2CP specification for details. + Support by the SAM server is optional, it will ignore these options if unsupported.