At 2:26 PM +0200 1/4/00, shay man wrote:
> Fixing the reading classes seems to me like quite a long task, as it
>involves changing all the calls to open and read the sockets, to
>non-blocking ones.
> If there is a version that already implemented that, or if someone
>has already done this, I will be happy to know about it.
I doubt it. It would help if the indexer was multithreaded, but that
also should explain why the connections work the way they do. Since
it's one thread, it has to wait for the connection to go through,
transfer, etc. before it can go to another connection.
Now whether the timeout code is correct or not is another matter. The
volume of questions about it leads me to believe there are problems
in it somewhere. After all, you should supposedly be able to change
the timeout... ;-)
So one really *good* thing would be for someone to test out some of
the connection code and see why it doesn't timeout well. (I'm the
last person who we want to touch it!)
-Geoff
------------------------------------
To unsubscribe from the htdig3-dev mailing list, send a message to
[EMAIL PROTECTED]
You will receive a message to confirm this.
