- May 07, 2004
-
- May 06, 2004
-
- May 05, 2004
-
-
* netDb.failedPeers (how many peers didn't reply to a lookup in time) * netDb.searchCount (how many searches we send out in a 3 hour period) probabalistically include the leaseSet of the sender in the garlic sent to a peer if the client requests it to be included (aka if they want replies). By default, this is enabled (disable by setting the I2CP prop "shouldBundleReplyInfo=false"). Also, by default the probability is 30% (w00 h00, arbitrary values!), which can be overridden via the I2CP prop "bundleReplyInfoProbability=80" (or =10, or =100, etc). The tradeoff here is quicker replies in exchange for bandwidth (the dbStore). Yeah, it'd be nice if there were something keeping track of which leaseSet each client sent to each peer so that it could explicitly include it only if it were necessary, but for now that's probably overkill.
- May 04, 2004
-
- May 03, 2004
-
-
* don't create excess I2PAppContexts (if any old context will do, use the global) keep track of keys per spec (when DESTINATION=blah, create (or reuse) the destination private keys). we still need to persist this data though. * the DESTINATION in the SESSION STATUS is now the same as the one sent in the SESSION CREATE, /not/ the base64 of the private key, per spec * enum is a reserved word in 1.5, so s/enum/names/ for future compatability * logging
-