From d29f9409bf23bda62179b891516294541d03efe0 Mon Sep 17 00:00:00 2001 From: jrandom Date: Tue, 20 Jul 2004 21:16:30 +0000 Subject: [PATCH] include some basic I2CP info --- core/java/src/net/i2p/client/package.html | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/core/java/src/net/i2p/client/package.html b/core/java/src/net/i2p/client/package.html index cbbb160ae..d13f7478d 100644 --- a/core/java/src/net/i2p/client/package.html +++ b/core/java/src/net/i2p/client/package.html @@ -29,4 +29,15 @@ but there are three other subpackages that are helpful. Specifically:

+ +

The {@link net.i2p.client.I2PSession} implementation itself communicates with +the I2P router by the I2CP (the client protocol). This is done over a +bidirectional TCP socket and never sends any private keys - all end to end +encryption is done transparently within the client's {@link net.i2p.client.I2PSession} +itself. Periodically the router will ask the client to authorize a new set of +tunnels to be allocated to the client, which the client can accept by sending a +{@link net.i2p.data.LeaseSet} signed by the {@link net.i2p.data.Destination}. In +addition, the router may on occation provide the client with an updated clock +offset so that the client can stay in sync with the network (even if the host +computer's clock is off).