forked from I2P_Developers/i2p.www
Switch in-i2p javadocs to my site instead of echelon's, which is down
This commit is contained in:
@@ -23,7 +23,7 @@ either protocol may be carried by either transport.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h2>{% trans %}Application Guide{% endtrans %}</h2>
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/datagram/package-summary.html',
|
||||
<p>{% trans url='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/datagram/package-summary.html',
|
||||
sam= site_url('docs/api/sam'),
|
||||
socks=site_url('docs/api/socks') -%}
|
||||
Applications written in Java may use the
|
||||
@@ -70,7 +70,7 @@ Applications may add 'from' and 'to' ports to the I2CP (gzip) header as describe
|
||||
the <a href="{{ i2cp }}#format">I2CP page</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans i2psession='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/I2PSession.html' -%}
|
||||
<p>{% trans i2psession='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/I2PSession.html' -%}
|
||||
There is no method within the datagram API to specify whether it is non-repliable (raw)
|
||||
or repliable. The application should be designed to expect the appropriate type.
|
||||
The I2CP protocol number or port should be used by the application to
|
||||
@@ -88,8 +88,8 @@ PROTO_DATAGRAM = 17
|
||||
PROTO_DATAGRAM_RAW = 18
|
||||
</li></ul>
|
||||
|
||||
<p>{% trans i2psession='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/I2PSession.html',
|
||||
i2psessionmuxed='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/I2PSessionMuxedImpl.html' -%}
|
||||
<p>{% trans i2psession='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/I2PSession.html',
|
||||
i2psessionmuxed='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/I2PSessionMuxedImpl.html' -%}
|
||||
The protocols and ports may be set in I2CP's
|
||||
<a href="{{ i2psession }}">I2PSession API</a>,
|
||||
as implemented in
|
||||
|
@@ -4,7 +4,7 @@
|
||||
|
||||
<h2>{% trans %}Note{% endtrans %}</h2>
|
||||
|
||||
<p>{% trans streaming=site_url('docs/api/streaming'), api='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
<p>{% trans streaming=site_url('docs/api/streaming'), api='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
The ministreaming library has been enhanced and extended by the
|
||||
"full" <a href="{{ streaming }}">streaming library</a>.
|
||||
Ministreaming is deprecated and is incompatible with today's applications.
|
||||
@@ -42,7 +42,7 @@ messages sent (or include any application level ACK or SACK), so it must wait
|
||||
on average twice the time it takes to send a message before sending another.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans api='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/package-summary.html',
|
||||
<p>{% trans api='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/streaming/package-summary.html',
|
||||
samv3=site_url('docs/api/samv3') -%}
|
||||
Even with those issues, the ministreaming library performs quite well in many
|
||||
situations, and its <a href="{{ api }}">API</a>
|
||||
|
@@ -389,7 +389,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
RESULT values
|
||||
|
@@ -446,7 +446,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
----------------------------------------------------------------------
|
||||
RESULT values
|
||||
|
@@ -542,7 +542,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Sign
|
||||
optionally followed by the <a href="{{ site_url('docs/spec/common-structures') }}#struct_OfflineSignature">Offline Signature</a>,
|
||||
which is 663 or more bytes in binary and 884 or more bytes in base 64,
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
</p><p>
|
||||
If the signing private key is all zeros, the
|
||||
@@ -605,7 +605,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Sign
|
||||
optionally followed by the <a href="{{ site_url('docs/spec/common-structures') }}#struct_OfflineSignature">Offline Signature</a>,
|
||||
which is 663 or more bytes in binary and 884 or more bytes in base 64,
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
</p><p>
|
||||
If the SESSION CREATE contained a signing private key of all zeros and
|
||||
@@ -1064,7 +1064,7 @@ CREATE command with PORT and HOST options:
|
||||
optionally followed by the <a href="{{ site_url('docs/spec/common-structures') }}#struct_OfflineSignature">Offline Signature</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
</p><p>
|
||||
Offline signatures are only supported for RAW datagrams.
|
||||
@@ -1446,7 +1446,7 @@ followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_Priv
|
||||
followed by the <a href="{{ site_url('docs/spec/common-structures') }}#type_SigningPrivateKey">Signing Private Key</a>,
|
||||
which is 884 or more base 64 characters (663 or more bytes in binary),
|
||||
depending on signature type.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
The binary format is specified in <a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/PrivateKeyFile.html">Private Key File</a>.
|
||||
|
||||
</p><p>
|
||||
DEST GENERATE does not require that a session has been created first.
|
||||
|
@@ -65,11 +65,11 @@ streaming library, to be interpreted by I2CP.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans i2cp=site_url('docs/protocol/i2cp'),
|
||||
i2psktmf='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html',
|
||||
i2psktm='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PSocketManager.html',
|
||||
i2psess='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/I2PSession.html',
|
||||
i2pskt='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PSocket.html',
|
||||
i2psskt='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PServerSocket.html' -%}
|
||||
i2psktmf='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html',
|
||||
i2psktm='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/streaming/I2PSocketManager.html',
|
||||
i2psess='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/I2PSession.html',
|
||||
i2pskt='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/streaming/I2PSocket.html',
|
||||
i2psskt='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/streaming/I2PServerSocket.html' -%}
|
||||
The standard interface to the streaming lib is for the application to use the
|
||||
<a href="{{ i2psktmf }}">I2PSocketManagerFactory</a> to create an
|
||||
<a href="{{ i2psktm }}">I2PSocketManager</a>. The application then asks the
|
||||
@@ -79,7 +79,7 @@ can then setup connections with an <a href="{{ i2pskt }}">I2PSocket</a> or
|
||||
receive connections with an <a href="{{ i2psskt }}">I2PServerSocket</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/streaming/package-summary.html' -%}
|
||||
Here are the <a href="{{ url }}">full streaming library Javadocs</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
@@ -89,7 +89,7 @@ For a good example of usage, see the i2psnark code.
|
||||
|
||||
|
||||
<h3 id="options">{% trans %}Options and Defaults{% endtrans %}</h3>
|
||||
<p>{% trans i2psktmf='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html' -%}
|
||||
<p>{% trans i2psktmf='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/streaming/I2PSocketManagerFactory.html' -%}
|
||||
The options and current default values are listed below.
|
||||
Options are case-sensitive and may be set for the whole router, for a particular client, or for an individual socket on a
|
||||
per-connection basis.
|
||||
|
@@ -364,7 +364,7 @@ as is done in our Java packages.
|
||||
As always, state management is the difficult part.
|
||||
{%- endtrans %}</p>
|
||||
<p>
|
||||
See also: <a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/Router.html">the Router javadocs</a>.
|
||||
See also: <a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/router/Router.html">the Router javadocs</a>.
|
||||
</p>
|
||||
|
||||
{% endblock %}
|
||||
|
@@ -201,7 +201,7 @@ This is implementation-dependent.
|
||||
<a href="{{ site_url('docs/spec/common-structures') }}#struct_RouterInfo">{% trans %}RouterInfo specification{% endtrans %}</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/router/RouterInfo.html">{% trans %}RouterInfo Javadoc{% endtrans %}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/router/RouterInfo.html">{% trans %}RouterInfo Javadoc{% endtrans %}</a>
|
||||
</p>
|
||||
|
||||
|
||||
@@ -248,9 +248,9 @@ In addition to these leases, the LeaseSet includes:
|
||||
<a href="{{ site_url('docs/spec/common-structures') }}#struct_LeaseSet">{% trans %}LeaseSet specification{% endtrans %}</a>
|
||||
</p>
|
||||
<p>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/Lease.html">{% trans %}Lease Javadoc{% endtrans %}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/Lease.html">{% trans %}Lease Javadoc{% endtrans %}</a>
|
||||
<br />
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/LeaseSet.html">{% trans %}LeaseSet Javadoc{% endtrans %}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/LeaseSet.html">{% trans %}LeaseSet Javadoc{% endtrans %}</a>
|
||||
</p>
|
||||
|
||||
<p>{% trans -%}
|
||||
|
@@ -63,7 +63,7 @@ See <a href="#notes">below</a> for notes on minor changes since the paper was pu
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<h2>{% trans %}Profiles{% endtrans %}</h2>
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/router/peermanager/PeerProfile.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/router/peermanager/PeerProfile.html' -%}
|
||||
Each peer has a set of data points collected about them, including statistics
|
||||
about how long it takes for them to reply to a network database query, how
|
||||
often their tunnels fail, and how many new peers they are able to introduce
|
||||
@@ -142,7 +142,7 @@ speed calculation meets or exceeds the median of all peers.
|
||||
<li>{% trans %}A peer is considered "standard" if it is not "high capacity"{% endtrans %}</li>
|
||||
</ul>
|
||||
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/router/peermanager/ProfileOrganizer.html' -%}
|
||||
<p>{% trans url='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/router/peermanager/ProfileOrganizer.html' -%}
|
||||
These groupings are implemented in the router's
|
||||
<a href="{{ url }}">ProfileOrganizer</a>.
|
||||
{%- endtrans %}</p>
|
||||
|
@@ -90,11 +90,11 @@ HTTP Bidir Proxy
|
||||
</li><li>
|
||||
<a href="{{ spec_url('streaming') }}">{{ _('Streaming Protocol Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/client/streaming/package-summary.html">{{ _('Streaming Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/client/streaming/package-summary.html">{{ _('Streaming Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('datagrams') }}">{{ _('Datagrams') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/client/datagram/package-summary.html">{{ _('Datagram Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/client/datagram/package-summary.html">{{ _('Datagram Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Client-to-Router Interface API and Protocol{% endtrans %}</h3>
|
||||
@@ -107,11 +107,11 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ spec_url('i2cp') }}">{{ _('I2CP Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/client/package-summary.html">{{ _('I2CP API Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/client/package-summary.html">{{ _('I2CP API Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('common-structures') }}">{{ _('Common data structures specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}End-to-End Encryption{% endtrans %}</h3>
|
||||
@@ -141,13 +141,13 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ spec_url('i2np') }}">{{ _('I2NP Specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/i2np/package-summary.html">{{ _('I2NP Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/i2np/package-summary.html">{{ _('I2NP Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('common-structures') }}">{{ _('Common data structures specification') }}</a>
|
||||
</li><li>
|
||||
<a href="{{ spec_url('encryptedleaseset') }}">{{ _('Encrypted Leaseset specification') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/data/package-summary.html">{{ _('Data Structures Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Tunnels{% endtrans %}</h3>
|
||||
@@ -184,11 +184,11 @@ Traditionally used only by Java applications and higher-level APIs.
|
||||
</li><li>
|
||||
<a href="{{ site_url('docs/how/cryptography') }}#udp">{{ _('SSU transport encryption') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/transport/package-summary.html">{{ _('Transport Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/router/transport/package-summary.html">{{ _('Transport Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/transport/ntcp/package-summary.html">{{ _('NTCP Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/router/transport/ntcp/package-summary.html">{{ _('NTCP Javadoc') }}</a>
|
||||
</li><li>
|
||||
<a href="http://{{ i2pconv('echelon.i2p/javadoc') }}/net/i2p/router/transport/udp/package-summary.html">{{ _('SSU Javadoc') }}</a>
|
||||
<a href="http://{{ i2pconv('idk.i2p/javadoc-i2p') }}/net/i2p/router/transport/udp/package-summary.html">{{ _('SSU Javadoc') }}</a>
|
||||
</li></ul>
|
||||
|
||||
<h3>{% trans %}Other Router Topics{% endtrans %}</h3>
|
||||
|
@@ -140,7 +140,7 @@ It also maintains a reverse-lookup map to implement rapid reverse lookups.
|
||||
|
||||
<h3>{{ _('Other Naming Service Facilities') }}</h3>
|
||||
|
||||
<p>{% trans nsjavadocs='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/naming/package-summary.html' -%}
|
||||
<p>{% trans nsjavadocs='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/naming/package-summary.html' -%}
|
||||
The lookup is case-insensitive.
|
||||
The first match is used, and conflicts are not detected.
|
||||
There is no enforcement of naming rules in lookups.
|
||||
|
@@ -15,7 +15,7 @@ I2CP to tell the client when any messages have arrived, and to request authoriza
|
||||
for some tunnels to be used.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans url='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/client/package-summary.html',
|
||||
<p>{% trans url='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/client/package-summary.html',
|
||||
libi2cp='http://git.repo.i2p/w/libi2cp.git',
|
||||
streaming=site_url('docs/api/streaming') -%}
|
||||
The protocol itself is implemented in Java, to provide the
|
||||
|
@@ -19,7 +19,7 @@ through multiple hops to the ultimate destination.
|
||||
Priority is only used locally at the origin, i.e. when queuing for outbound delivery.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans outnetmessage='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/router/OutNetMessage.html' -%}
|
||||
<p>{% trans outnetmessage='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/router/OutNetMessage.html' -%}
|
||||
The priorities listed below may not be current and are subject to change.
|
||||
See the <a href="{{ outnetmessage }}">OutNetMessage Javadocs</a>
|
||||
for the current priority settings.
|
||||
|
@@ -22,7 +22,7 @@ as a replacement for the
|
||||
As modPow() is a significant computational portion of many crypto operations, this is of significant benefit.
|
||||
{%- endtrans %}</p>
|
||||
|
||||
<p>{% trans nativebigint='http://'+i2pconv('echelon.i2p/javadoc')+'/net/i2p/util/NativeBigInteger.html',
|
||||
<p>{% trans nativebigint='http://'+i2pconv('idk.i2p/javadoc-i2p')+'/net/i2p/util/NativeBigInteger.html',
|
||||
bigint='http://download.oracle.com/javase/1.5.0/docs/api/java/math/BigInteger.html#modPow%28java.math.BigInteger,%20java.math.BigInteger%29' -%}
|
||||
The standard I2P installation includes about 20 versions of the library for different platforms,
|
||||
each about 50KB, inside the jbigi.jar file.
|
||||
|
Reference in New Issue
Block a user