I doubt that other server softwares are handling connections the way I do - nonblocking. It's very uncommon as handling non blocking sockets is much more difficult that handling plain blocking sockets (also dproxy is working in nonblocking mode, however implementation there might not be valid)... use of non blocking sockets gives quite a few advantages: you can handle several connections with one thread if needed, you're always aware how much data you've sent to socket... So far noone has reported any compatability problems with real clients. I will test the dproxy tonight to make sure that origin of this problem is not on the server-side.
There are some other known issues in dproxy2 as well.. I might fix them one day, but until then it's what it is.
|