- Jul 31, 2004
-
-
-
- I2PSocketServer.py - I2PBaseHTTPServer.py - I2PSimpleHTTPServer.py - I2PCGIHTTPServer.py difference being that these new modules are not hacks of the original python server modules, rather, they subclass the python server modules; this overcomes the Fear and Loathing expressed by some regarding multiplicity of licenses, and apart from that, is a better idea anyway. Only danger being if the modules in later Python releases change substantially, these modules could get broken.
-
- Jul 30, 2004
-
- Jul 29, 2004
-
-
-
avoid the race that could corrupt local transfers by using a single thread to receive notifications of message availability (and in turn fetch that data) the old way fired off a new (very short lived) thread for each message received, and if two happened really really quickly, they'd both lock on the mutex and the order would be undefined this avoids that. thanks to oOo et al for pestering me and sending in logs :)
-
* drop the outbound message as soon as it expires rather than transferring an expired message * drop hard any outbound message that takes us over 5 seconds to process (if we have a 5s message processing time, we do no one any good) * don't try to resend (only useful when dealing with multiple transports - aka insufficiently tested code) * don't republish netDb messages as often
-
- Jul 28, 2004
-