Tonight I completed the change I've been working on for last few days. SpiderSilk client libraries have been changed from Indy to native .NET sockets (System.Net.Socket).
Previous network layer on the client has been implemented using Indy since the early beginning of the project. Indy still remains the core of the server side Connection framework and the stub of the protocol. Replacement came as the first step in the long-term plan to keep the SpiderSilk client as much as possible under the System namespace, that is - a pure .NET app. We are still using blocking sockets as the whole architecture has been built upon Indy - which, of course, uses blocking sockets. Performance wise there's no much difference, although I've noticed slight delay while establishing the connection at the start-up. Other than that - everything works perfectly.
