- Oct 24, 2004
-
-
* Allow explicit inclusion of session tags in the SDK, enabling the resending of tags bundled with messages that would not otherwise be ACKed. * Don't force mode=guaranteed for end to end delivery - if mode=bestEffort no DeliveryStatusMessage will be bundled (and as such, client apps using it will need to do their own session tag ack/nack). * Handle client errors when notifying them of message availability. * New StreamSinkSend which sends a file to a destination and disconnects. * Update the I2PSocketManagerFactory to build the specific I2PSocketManager instance based on the "i2p.streaming.manager" property, containing the class name of the I2PSocketManager implementation to instantiate.
-
- Oct 22, 2004
-
- Oct 21, 2004
-
- Oct 20, 2004
-
- Oct 18, 2004
-
- Oct 17, 2004
-
- Oct 16, 2004
-
- Oct 15, 2004
-
- Oct 14, 2004
-
-
* Allow for a configurable tunnel "growth factor", rather than trying to achieve a steady state. This will let us grow gradually when the router is needed more, rather than blindly accepting the request or arbitrarily choking it at an averaged value. Configure this with "router.tunnelGrowthFactor" in the router.config (default "1.5"). * Adjust the tunnel test timeouts dynamically - rather than the old flat 30s (!!!) timeout, we set the timeout to 2x the average tunnel test time (the deviation factor can be adjusted by setting "router.tunnelTestDeviation" to "3.0" or whatever). This should help find the 'good' tunnels. * Added some crazy debugging to try and track down an intermittent hang.
- Oct 13, 2004
-
- Oct 12, 2004
-
-
* Disable the probabalistic drop by default (enable via the router config property "tcp.dropProbabalistically=true") * Disable the actual watchdog shutdown by default, but keep track of more variables and log a lot more when it occurs (enable via the router config property "watchdog.haltOnHang=true") * Implement some tunnel participation smoothing by refusing requests probabalistically as our participating tunnel count exceeds the previous hour's, or when the 10 minute average tunnel test time exceeds the 60 minute average tunnel test time. The probabilities in both cases are oldAverage / #current, so if you're suddenly flooded with 200 tunnels and you had previously only participated in 50, you'll have a 25% chance of accepting a subsequent request.
- Oct 11, 2004
-
- Oct 10, 2004
-
-
-
* Added a watchdog timer to do some baseline liveliness checking to help debug some odd errors. * Added a pair of summary stats for bandwidth usage, allowing easy export with the other stats ("bw.sendBps" and "bw.receiveBps") * Trimmed another memory allocation on message reception.
-
- Oct 08, 2004
-
- Oct 07, 2004
-