🚀 go-pugleaf

"Guenter Stubbe" <no-spam@no.spam.com> wrote in message
news:42a475d3$1@newsgroups.borland.com...

> If I call the Write method two or more times successively, not
> all data is transfered (in my application). If I code a Sleep(50)
> between them, the transfer works.

I have never had to use Sleep() with TWinSocketStream.  Successive
reads/writes without sleeping has always worked fine for me without problem.
Please show your actual code.

> The Read method of TWinSocketStream can return a "-1"?

The only way for Read() to return -1 is if a socket error occured.  But if
that happened, you should be getting a ESocketError exception as well.

> In the german help there is a hint, that the WaitForData method
> should be called always, if a Read or Write method is called
> afterwards: In my code, the WaitForData only works for the Read
> method...

That is correct.  The help is wrong.

> What is a usual size for packets written or read via TWinSocketStream?

Makes no difference.


Gambit