From time to time in my program I encounter strange error on connecting.
Here's a piece of socket log:
2010-04-16 10:55:50SocketChangeState, wsClosed - wsOpened
2010-04-16 10:55:50TWSocket will connect to 200.255.94.90:2101
2010-04-16 10:55:50
*something wrong with my previous mail, retrying...*
From time to time in my program I encounter strange error on connecting.
Here's a piece of socket log:
2010-04-16 10:55:50SocketChangeState, wsClosed - wsOpened
2010-04-16 10:55:50TWSocket will connect to
*something wrong with my previous mail, retrying...*
From time to time in my program I encounter strange error on connecting.
Here's a piece of socket log:
2010-04-16 10:55:50 SocketChangeState, wsClosed - wsOpened
2010-04-16 10:55:50 TWSocket will connect to 200.255.94.90:2101
Hello:
It seems like the connection was dropped unexpectedly by the other
side. Socket operation on non-socket means that a WinSock call was sent on a
closed socket or invalid handle.
dZ.
On Apr 16, 2010, at 03:48, Anton Sviridov wrote:
*something wrong with my previous
Hi Graham,
Yes TFileStream will use disk. If you have only small transfers you can do
as you do now. If you worry about speed then you could gain speed a lot by
using pointers to your own memory location instead of TStream.
--
mvg, Wilfried
http://www.mestdagh.biz
-Oorspronkelijk
Anton Sviridov wrote:
wilfried, dZ, the strangest thing is that socket is created and
connected directly before the bug. Here is what happens next:
Can you tell what is being called exactly at the moment the error
occurs? Try adding the ICS source directory to your Library Path and
setting
