jrandom c6bb8f09ca 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 :)

2004-07-29 20:02:12 +00:00

..

src/net/i2p

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)

2004-07-29 20:02:12 +00:00

test/net/i2p

new constructor

2004-06-22 04:53:22 +00:00

build.xml

target=1.3 and source=1.3, not target=1.1 and source=1.3

2004-07-12 16:39:22 +00:00