>Asside from that, the fact that you have to include a line number as a
>parameter to the command suggests a poorly designed protocol to begin with.
>If you are sending the lines in order from the client, then there is no need
>to specify the line numbers at all. Like I mentioned before, you should not
>be sending the lines individually as separate commands to begin with. Send
>them in a single command, ie:
Agreed. I started with sending the entire file at once (with the features I knew of from the existing system I need to replace) and ran into problems when the files were beyond a few K in size. Our installation of Indy lacks the demo files, and I have been unable to connect to a web site with the missing demo code. I have been reading the help files and learning other ways to do things.
Anyway, the fact of getting "good" return codes long before the commands were complete remains a mystery. I would love to learn how that happened, but I am moving on.
I am using writestream in the client and readstream in the server. I am using OnExecute instead of command handlers in the server. But none of that matters. Having abandoned the one line at a time (which worked quite well as long as I was willing to put sleep commands in the code) I have a new problem that doesn't even allow the new method to come into play.
MyClient.Connect;
results in:
Socket error #10061
connection refused
Why is this?
Thanks,
Jon
