🚀 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

Guenter Stubbe wrote:

>I have questions according to the usage of TWinSocketStream.
>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. Why? What is a good value for the Sleep?

What timeout value are you giving Write, and how big is your buffer,
and how fast is your connection ?
See the TimeOut property.

>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:

Yes, should do so. It doesn't sound like Wait waits for write
completion (Write does that), just waits for the socket to be ready to
send.

>What is a usual size for packets written or read via TWinSocketStream?
>I have no idea and need a starting point.

What's best depends on your connection speed.
I would probably set the buffer size to 1/2 the timeout value, or the
timeout to twice the max buffer size (as adjusted by the expected
connection rate). And, again, as adjusted by human factors. I don't
want the timeout so large that the user thinks I locked up. And, I
don't want the timeout so small that the user can't possibly notice
it.

Remy Lebeau (TeamB) schrieb:
...
> 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.

With the knowledge, that the Sleep is not needed I have detected the 
error in my application.

Thank you very much for your answers.

Bob Gonder schrieb:
> Guenter Stubbe wrote:
> 
> 
>>I have questions according to the usage of TWinSocketStream.
>>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. Why? What is a good value for the Sleep?
> 
> 
> What timeout value are you giving Write, and how big is your buffer,
> and how fast is your connection ?
> See the TimeOut property.
> 

The first question is obsolete, becaus with the hint from Remy Lebeau I 
found the Write works without the Sleep. I have made an error in parsing 
the buffer ...

> 
>>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:
> 
> 
> Yes, should do so. It doesn't sound like Wait waits for write
> completion (Write does that), just waits for the socket to be ready to
> send.
> 
> 

Ok.


>>What is a usual size for packets written or read via TWinSocketStream?
>>I have no idea and need a starting point.
> 
> 
> What's best depends on your connection speed.
> I would probably set the buffer size to 1/2 the timeout value, or the
> timeout to twice the max buffer size (as adjusted by the expected
> connection rate). And, again, as adjusted by human factors. I don't
> want the timeout so large that the user thinks I locked up. And, I
> don't want the timeout so small that the user can't possibly notice
> it.
> 


I expect the size of the buffer is in byte and the timeout value in ms.

Thank you very much for your help.