jrandom authored 20 years ago and zzz committed 20 years ago

instead of the standard 'httpclient 4444' or 'httpclient 4444 squid.i2p', you can now specify a comma delimited list of outproxies:
'httpclient 4444 squid.i2p,www1.squid.i2p,www2.squid.i2p' and each individual http request goes through a randomly selected proxy
there are a few general issues with this, such as a lack of affinity (web applications that require a session to always come from a single IP address will break)
but it should work most of the time.

jrandom authored 20 years ago and zzz committed 20 years ago

disabled by default (enable through router.config 'netDb.shouldHarvest=true').
useful if you want to harvest the published router stats, since otherwise you could have data from a few hours back

jrandom authored 20 years ago and zzz committed 20 years ago

* build an i2ptunnel.war

jrandom authored 20 years ago and zzz committed 20 years ago

* don't use static props on the I2PTunnel for I2CP / etc so that we can safely keep multiple instances alive
* propogate errors (if the I2CP host isnt reachable, the socket manager
won't be created) and handle appropriately

jrandom authored 20 years ago and zzz committed 20 years ago

logging

jrandom authored 20 years ago and zzz committed 20 years ago

increase the (essentially) arbitrary choke on message send times (which has caused some reliability problems under load)

jrandom authored 20 years ago and zzz committed 20 years ago

or even whether to have the blocking action timeout and close the socket after
a certain delay
* refactored the I2PSocketOptions to be more actively used
* added a pair of ministreaming lib demo apps:
- StreamSinkServer listens to a destination and dumps any data it receives on a socket to a per-socket file
- StreamSinkClient sends a destination a specified number of random bytes, then disconnects