🚀 go-pugleaf

"Marijan Sever" <marijan.sever@codel.hr> wrote in message 
news:4789d472@newsgroups.borland.com...

> UPS...? What are the other ways?

Sorry, I forgot that UDP does not have as many options as TCP.  In TCP, you 
could use a TStream, TIdBytes, or String.  In UDP, you don't have the 
TStream option.

> I have already try exactly as in your sample and in the debugger
> mode in the Local variable window I have as follows:
>
>      cbuf
>      |-----Data
>            |------[0]-------'\x01'1(0x01)
>            |------[1]-------'\x00'0(0x00)
>
> ...and nothing else. Have you tried this and get other results?

Did you try expanding the range of the Inspector to 8 slots?  You know the 
TIdBytes is allocated to 8 bytes long, but only 2 bytes are being displayed. 
That should tell you that it is the Inspector, not the code, that is 
stopping on a 0x00 byte.

>    pUDPSock->ClSock->ReceiveBuffer(RxBuf,500);

What are you setting the Length of RxBuf to beforehand.  You have to set it 
before calling ReceiveBuffer() so it knows the maximum numbe of bytes to 
read.  What value is ReceiveBuffer() returning?  That is the number of bytes 
that are actually read into the TIdBytes.  You should be resizing the 
TIdBytes to the desired Length every time beforehand, and then resizing it 
to whatever ReceiveBuffer() returns.  ReceiveBuffer() will not size the 
TIdBytes for you.  For example:

    try
    {
        RxBuf.Length = 8192;
        RxBuf.Length = pUDPSock->ClSock->ReceiveBuffer(RxBuf, 500);
        //...
    }
    catch(...)
    {
        //...
    }

> catch (Exception &E)

Always catch exceptions by 'const' reference instead:

    catch (const Exception &E)


Gambit