Mark D. Lincoln wrote:
> Ciaran,
>
> Since we have created both the server and client applications, this
> is not our problem. Also, since this occurs in Indy 10 and not in
> Indy 9, there has got to be something up with the socket code in Indy
> 10.
There is no general problem with Indy 10's TIdHTTP. I have a couple of
applications that use it to automate some processes, one of which pulls
a pile of web pages off a server once a day after an average 23-hour
delay between the web site getting updated. Each download is, however,
wrapped in a try...except whereby if there was a "connection reset by
peer", it would retry after a short delay - you should consider
implementing this anyway, to deal with network problems, and it should
sort your issue out.
You could check it out further by running the free Ethereal packet
sniffer to see exactly why the connection is being reset.
If you showed your client code, someone here may spot a programming
error.
Ciaran
