Another short question. In my test server I put kbmMWTCPServerTransport and it works fine with client which has kbmMWTCPIPIndyClientTransport. However If I replace client Indy transport with kbmMWTCPClientTransport (and re-connect the properties), client cannot connect to the server. I’ve tried changing different properties but it still cannot connect.
Aren’t kbmMWTCPServerTransport and kbmMWTCPClientTransport meant to work together?
They are as such not specifically meant to work together. They are separate entities. TCP Server is a IOCP (on Windows) based server transport, while TCP Client is a potential replacement for Indy client transports.
So you can mix and match as you see fit.
There are features in Indy TCP client which are not available in TCP Client as it is still work in progress.