forked from I2P_Developers/i2p.www
new streaming option
This commit is contained in:
@ -1,7 +1,7 @@
|
||||
{% extends "_layout.html" %}
|
||||
{% block title %}Streaming Library{% endblock %}
|
||||
{% block content %}
|
||||
Updated August 2010, current as of router version 0.8
|
||||
Updated June 2012, current as of router version 0.9.1
|
||||
<h2>Overview</h2>
|
||||
|
||||
<p>
|
||||
@ -114,10 +114,13 @@ Also note that many options only apply to servers listening for incoming connect
|
||||
<tr><th>Option</th><th>Default</th><th>Notes</th>
|
||||
</tr>
|
||||
<tr><td>i2cp.accessList</td><td>null</td><td>Comma- or space-separated list of Base64 peer Hashes used for either access list or blacklist
|
||||
As of release 0.7.13.
|
||||
</td></tr><tr><td>i2cp.enableAccessList</td><td>false
|
||||
</td><td>Use the access list as a whitelist for incoming connections
|
||||
As of release 0.7.13.
|
||||
</td></tr><tr><td>i2cp.enableBlackList</td><td>false
|
||||
</td><td>Use the access list as a blacklist for incoming connections
|
||||
As of release 0.7.13.
|
||||
</td></tr><tr><td>i2p.streaming.answerPings</td><td>true</td><td>Whether to respond to incoming pings
|
||||
</td></tr><tr><td>i2p.streaming.bufferSize</td><td>64K</td><td>
|
||||
How much transmit data (in bytes) will be accepted that hasn't been written out yet.
|
||||
@ -136,6 +139,10 @@ Also note that many options only apply to servers listening for incoming connect
|
||||
or that many milliseconds pass, and include any initial data with the SYN.
|
||||
</td></tr><tr><td>i2p.streaming.connectTimeout</td><td>5*60*1000</td><td>
|
||||
How long to block on connect, in milliseconds. Negative means indefinitely. Default is 5 minutes.
|
||||
</td></tr><tr><td>i2p.streaming.enforceProtocol</td><td>false</td><td>Whether 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.
|
||||
As of release 0.9.1.
|
||||
</td></tr><tr><td>i2p.streaming.inactivityAction</td><td>2 (send) </td><td>(0=noop, 1=disconnect)
|
||||
What to do on an inactivity timeout - do nothing, disconnect, or send a duplicate ack.
|
||||
</td></tr><tr><td>i2p.streaming.inactivityTimeout</td><td>90*1000
|
||||
@ -150,17 +157,23 @@ Also note that many options only apply to servers listening for incoming connect
|
||||
</td></tr><tr><td>i2p.streaming.maxConcurrentStreams</td><td>-1 </td><td>(0 or negative value means unlimited)
|
||||
This is a total limit for incoming and outgoing combined.
|
||||
</td></tr><tr><td>i2p.streaming.maxConnsPerMinute</td><td>0 </td><td>Incoming connection limit (per peer; 0 means disabled)
|
||||
As of release 0.7.14.
|
||||
</td></tr><tr><td>i2p.streaming.maxConnsPerHour</td><td>0 </td><td>(per peer; 0 means disabled)
|
||||
As of release 0.7.14.
|
||||
</td></tr><tr><td>i2p.streaming.maxConnsPerDay</td><td>0 </td><td>(per peer; 0 means disabled)
|
||||
As of release 0.7.14.
|
||||
</td></tr><tr><td>i2p.streaming.maxMessageSize</td><td>1730</td><td>The MTU in bytes.
|
||||
</td></tr><tr><td>i2p.streaming.maxResends</td><td>8
|
||||
</td><td>
|
||||
Maximum number of retransmissions before failure.
|
||||
</td></tr><tr><td>i2p.streaming.maxTotalConnsPerMinute</td><td>0 </td><td>Incoming connection limit (all peers; 0 means disabled)
|
||||
As of release 0.7.14.
|
||||
</td></tr><tr><td>i2p.streaming.maxTotalConnsPerHour</td><td>0 </td><td>(all peers; 0 means disabled)
|
||||
Use with caution as exceeding this will disable a server for a long time.
|
||||
As of release 0.7.14.
|
||||
</td></tr><tr><td>i2p.streaming.maxTotalConnsPerDay</td><td>0 </td><td>(all peers; 0 means disabled)
|
||||
Use with caution as exceeding this will disable a server for a long time.
|
||||
As of release 0.7.14.
|
||||
</td></tr><tr><td>i2p.streaming.maxWindowSize</td><td>128
|
||||
</td></tr><tr><td>i2p.streaming.profile</td><td>1 (bulk)</td><td>(2=interactive not supported)
|
||||
This doesn't currently do anything, but setting it to a value other than 1 will cause an error.
|
||||
|
Reference in New Issue
Block a user