[alexti]

Originally posted by Norfleet:
This strongly suggests that it's a Windoze-specific problem, as Windoze networking code and networking code for unices are completely different: Everything else would largely be the same, except for the network code, which I currently suspect is the culprit.

If you're talking about the applications network code, you can write pretty much the same code. Either OS supports berkeley sockets API, so unless Illwinter intentionally implements networking differently, it should be the same.

TCP transport implementation (that comes with OS) is a different thing though. But then it's not clear why only Dom2 suffers from the problems. Though Windows is not as good at networking, the degree of problems is unreasonable even for Windows. I'm puzzled about what it might be. Maybe some setsockopt option is different by default? SO_LINGER for example?