9 Commits

Author	SHA1	Message	Date
human	d7c3a53f2d	Initial implementation of read() timeout on I2PSocket. Let's see whether it ... could solve duck's problems with dangling threads... (human)	2004-04-21 17:56:16 +00:00
human	8038e1ee7d	I2PSocketManager.connect() should have thrown InterruptedIOException, and *not* ... InterruptedException (oops!) (human)	2004-04-20 15:38:55 +00:00
human	fb170e3c42	* Made I2PSocketManager.connect() throw several kinds of exceptions, for ... better error reporting; * Added an I2PSocketManager.destroySocketManager() method, that closes all the managed sockets and destroys the associated I2PSession. (human)	2004-04-19 21:45:04 +00:00
human	031338d84d	First step for the "connection refused" concept: incoming connections ... won't be accepted until the server app actually requires an I2PServerSocket from the I2PSocketManager. It allows both to add a little bit of functionality, and to fix a nasty bug: it was possible to hang an app that connects through the I2PSocketManager but actually doesn't accept() connections (if 2 connection requests were sent to the app, the I2PSocketManager got stuck waiting forever on I2PServerSocketImpl.getNewSocket()).	2004-04-16 03:31:13 +00:00
human	d2b09ecfda	* Fixed race that (maybe) caused the problems reported by aum on ... <http://dev.i2p.net/pipermail/i2p/2004-April/000214.html>; * slightly revised locking; * made accept() throw a ConnectException when the I2PServerSocket is closed. (human)	2004-04-14 15:28:02 +00:00
shendaras	51c49d7c1b	format (shendaras)	2004-04-10 11:50:11 +00:00
shendaras	8a8e68146f	beginning of format, updated imports. (shendaras)	2004-04-10 11:39:00 +00:00
jrandom	f37c0ed612	name all threads, and (nearly) always use I2PThread (in case we add some pooling/throttling/monitoring or whatnot later)	2004-04-09 01:22:04 +00:00
cvs_import	77bd69c5e5	beginning of branch i2p.i2p.i2p	2004-04-08 04:41:54 +00:00