From a5a0c8c83762ad8446c82482f7ea69e8d8f1ccbc Mon Sep 17 00:00:00 2001
From: jrandom <jrandom>
Date: Tue, 20 Jul 2004 21:31:57 +0000
Subject: [PATCH] moved minimal I2CP info to the I2PSession docs (since it is
 the one that implements it)

---
 core/java/src/net/i2p/client/I2PSession.java | 13 ++++++++++---
 core/java/src/net/i2p/client/package.html    | 10 +---------
 2 files changed, 11 insertions(+), 12 deletions(-)

diff --git a/core/java/src/net/i2p/client/I2PSession.java b/core/java/src/net/i2p/client/I2PSession.java
index bf517d7ca..bb26cbe54 100644
--- a/core/java/src/net/i2p/client/I2PSession.java
+++ b/core/java/src/net/i2p/client/I2PSession.java
@@ -17,10 +17,17 @@ import net.i2p.data.SessionKey;
 import net.i2p.data.SigningPrivateKey;
 
 /**
- * Define the standard means of sending and receiving messages on the 
- * I2P Network.
+ * <p>Define the standard means of sending and receiving messages on the 
+ * 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 {
     /** Send a new message to the given destination, containing the specified
diff --git a/core/java/src/net/i2p/client/package.html b/core/java/src/net/i2p/client/package.html
index d13f7478d..0bba369b1 100644
--- a/core/java/src/net/i2p/client/package.html
+++ b/core/java/src/net/i2p/client/package.html
@@ -31,13 +31,5 @@ but there are three other subpackages that are helpful.  Specifically:<ul>
 </ul></p>
 
 <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 
-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>
+the I2P router by the I2CP (the client protocol).</p>
 </body></html>