Hi, I am writing an application that makes use of the Indy tcp server (and client) components. I am using readln on the server to listen for commands from the client but I need the code to go off and check various things every so often if it hasn't recieved a command. I have specified a timeout value for the readln but it still insists on waiting until it has recieved something before it moves on. Is this behaviour intentional on the part of the component? And if so then what exactly is the timeout meant to do?
Note that the problem isn't with my server locking up until something is recieved or anything like that, it all works nicely except for no timeout occuring (as far as I can tell).
Thanks for bothering to read this far ;-)
Note that the problem isn't with my server locking up until something is recieved or anything like that, it all works nicely except for no timeout occuring (as far as I can tell).
Thanks for bothering to read this far ;-)