I2P_Developers/i2p.itoopie
3
0
Fork 0
Code Issues Pull Requests Actions 1 Packages Projects Releases Wiki Activity

moved minimal I2CP info to the I2PSession docs (since it is the one that implements it)

Browse Source
This commit is contained in:
jrandom
2004-07-20 21:31:57 +00:00
committed by zzz
parent 604bcd5874
commit a5a0c8c837
2 changed files with 11 additions and 12 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
core/java/src/net/i2p/client/I2PSession.java
View File

@ -17,10 +17,17 @@ import net.i2p.data.SessionKey;
import net.i2p.data.SigningPrivateKey; import net.i2p.data.SigningPrivateKey;
/** /**
* Define the standard means of sending and receiving messages on the * <p>Define the standard means of sending and receiving messages on the
* I2P Network. * I2P network by using 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 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).</p>
* *
* @author jrandom
*/ */
public interface I2PSession { public interface I2PSession {
/** Send a new message to the given destination, containing the specified /** Send a new message to the given destination, containing the specified

10
core/java/src/net/i2p/client/package.html
View File

@ -31,13 +31,5 @@ but there are three other subpackages that are helpful. Specifically:<ul>
</ul></p> </ul></p>
<p>The {@link net.i2p.client.I2PSession} implementation itself communicates with <p>The {@link net.i2p.client.I2PSession} implementation itself communicates with
the I2P router by the I2CP (the client protocol). This is done over a the I2P router by the I2CP (the client protocol).</p>
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).</p>
</body></html> </body></html>