diff --git a/www.i2p2/pages/i2cp.html b/www.i2p2/pages/i2cp.html index cc9f365f..f1401b6f 100644 --- a/www.i2p2/pages/i2cp.html +++ b/www.i2p2/pages/i2cp.html @@ -1,7 +1,7 @@ {% extends "_layout.html" %} {% block title %}I2CP{% endblock %} {% block content %} -Updated September 2012, current as of router version 0.9.2 +Updated November 2012, current as of router version 0.9.3

The I2P Client Protocol (I2CP) exposes a strong separation of concerns between the router and any client that wishes to communicate over the network. It enables @@ -112,8 +112,11 @@ a SessionConfig contained in a < Higher is higher priority. As of 0.9.4. i2cp.dontPublishLeaseSet true, false falseShould generally be set to true for clients and false for servers -i2cp.messageReliability  BestEffort, Guaranteed, NoneBestEffortGuaranteed is disabled; - None implemented in 0.8.1; the streaming lib default is None as of 0.8.1 +i2cp.messageReliability  BestEffort, NoneBestEffortGuaranteed is disabled; + None implemented in 0.8.1; the streaming lib default is None as of 0.8.1, the client side default is None as of 0.9.4 +i2cp.fastReceive true, falsefalseIf true, the router just sends the MessagePayload instead + of sending a MessageStatus and awaiting a ReceiveMessageBegin. + As of 0.9.4 explicitPeers  nullComma-separated list of Base 64 Hashes of peers to build tunnels through; for debugging only i2cp.usernamestring  For authorization, if required by the router (since 0.8.2). If the client is running in the same JVM as a router, this option is not required. @@ -161,6 +164,7 @@ Prior to that release, options with multi-byte characters were corrupted. The following options are interpreted on the client side, and will be interpreted if passed to the I2PSession via the I2PClient.createSession() call. The streaming lib should also pass these options through to I2CP. +Other implementations may have different defaults.

@@ -179,6 +183,10 @@ The streaming lib should also pass these options through to I2CP.
Client-side Options
i2cp.reduceQuantity0.7.111 to 51Tunnel quantity when reduced (applies to both inbound and outbound)
i2cp.encryptLeaseSet0.7.1true, false  falseEncrypt the lease
i2cp.leaseSetKey0.7.1   Base64 SessionKey (44 characters) +
i2cp.messageReliability  BestEffort, NoneNoneGuaranteed is disabled; + None implemented in 0.8.1; None is the default as of 0.9.4 +
i2cp.fastReceive0.9.4 true, falsetrueIf true, the router just sends the MessagePayload instead + of sending a MessageStatus and awaiting a ReceiveMessageBegin.

Note: All arguments, including numbers, are strings. True/false values are case-insensitive strings. diff --git a/www.i2p2/pages/i2cp_spec.html b/www.i2p2/pages/i2cp_spec.html index 312bafd7..bab1e486 100644 --- a/www.i2p2/pages/i2cp_spec.html +++ b/www.i2p2/pages/i2cp_spec.html @@ -1,7 +1,7 @@ {% extends "_layout.html" %} {% block title %}I2CP Specification{% endblock %} {% block content %} -Updated September 2012, current as of router version 0.9.2 +Updated November 2012, current as of router version 0.9.3

I2P Control Protocol (I2CP) Specification

Overview

@@ -87,7 +87,16 @@ Bandwidth Limits Message <---------------------

Outgoing Message

-

(existing session)

+

Existing session, with i2cp.messageReliability=none

+
+{% filter escape %}
+    Client                                           Router
+
+                           --------------------->  Send Message Message
+
+{% endfilter %}
+
+

Existing session, with i2cp.messageReliability=BestEffort

 {% filter escape %}
     Client                                           Router
@@ -99,15 +108,20 @@ Bandwidth Limits Message  <---------------------
   (succeeded)
 {% endfilter %}
 
-

-Note: As of release 0.8.1, the router does not send either Message Status Message if -i2cp.messageReliability=none. -

Incoming Message

-

(existing session)

+

Existing session, with i2cp.fastReceive=true (as of 0.9.4)

+
+{% filter escape %}
+    Client                                           Router
+
+ Message Payload Message  <---------------------
+
+{% endfilter %}
+
+

Existing session, with i2cp.fastReceive=false

 {% filter escape %}
     Client                                           Router
diff --git a/www.i2p2/pages/streaming.html b/www.i2p2/pages/streaming.html
index 3dac76c8..078230b0 100644
--- a/www.i2p2/pages/streaming.html
+++ b/www.i2p2/pages/streaming.html
@@ -1,7 +1,7 @@
 {% extends "_layout.html" %}
 {% block title %}Streaming Library{% endblock %}
 {% block content %}
-Updated September 2012, current as of router version 0.9.2
+Updated November 2012, current as of router version 0.9.3
 

Overview

@@ -148,6 +148,9 @@ See the javadocs for details. or that many milliseconds pass, and include any initial data with the SYN. i2p.streaming.connectTimeout5*60*1000 How long to block on connect, in milliseconds. Negative means indefinitely. Default is 5 minutes. +i2p.streaming.disableRejectLoggingfalse + Whether to disable warnings in the logs when an incoming connection is rejected due to connection limits. + As of release 0.9.4. i2p.streaming.enforceProtocolfalseWhether to listen only for the streaming protocol. Setting to true will prohibit communication with Destinations earlier than release 0.7.1 (released March 2009). Set to true if running multiple protocols on this Destination.