To tell you the truth, I must admit that my earlier post was mostly assumption based upon the behavior I saw. When I get a chance, I'll reload it on my development machine and do some sniffing into the processes.

That is, unless the XoloX crew makes us happy by releasing a bugfix first.

-3vi1
http://www.eternaldusk.com

This has nothing to do with Xolox and everything to do with winsock.

Sometimes TCP/IP connections on the windows stack will take awhile to close (sometimes a *long* while). If the app doesn't wait to close all sockets properly before terminating, it usually causes the winsock to crash!

Gnutella apps make so many connections that after a few hours the winsock is usually somewhat hosed. "Stuck" connections are common. Window's network stack just isn't designed for such heavy use. Some claim it's intentionally crippled for home versions of windows since Win2k/NT/XP server versions usually work better.