🚀 go-pugleaf

"Roberto Zais" <rzaiss@tiscali.it> wrote in message
news:421e4d30@newsgroups.borland.com...

> Perhaps in the example you provided is transmitted first of
> all an int that means Number of following bytes

That is the general assumption.

> Sorry, but maybe .. I realize now.  ReadInteger(true)  reads
> the first (8?) bytes of my proprietary protocol :-)

ReadInteger() reads 4 bytes, not 8.  An Integer is 4 bytes in size.

> Concerning the details :     my connection is with a remote peer directly
> interfaced to a serial line , it is a direct tunnelling and
> I speak using my own protocol .

Then I suggest that your do transmit an Integer specifying the number of
bytes to follow.

> I have experimented that the following solution seems working :
> is it correct? (ReadFromStack provides the number of bytes
> actually available)

Yes, it does specify the number of bytes actually read, but it doesn't tell
you how many individual packets are in that data.  Using the preceeding-int
approach, you can read each packet individually, or read a larger block and
then determine how many complete packets are contained in that block.

> Please, can you give me another advice ..
> (1)   if(TCPClient->Connected())      //esito == true )
> does not work

Yes, it does work.  Why do you think that it does not.

> Shall I use a  test like (1) or simply trap exceptions across
> every call following the Connect() ?

Connect() does throw an exception if the connection fails, so checking
Connected() after calling Connect() is redundant, but will still work
anyway.


Gambit