🚀 go-pugleaf

"Paul at NCF" <notplmacca@clara.co.uk> wrote in message
news:46e26004$1@newsgroups.borland.com...

> What I want to know is how this changes with Indy 10 and
> the TIdBytes parameter?

TIdBytes has a Length property.  That will tell you how many bytes are
available.  It also has a '[]' operator, so you can access the individual
bytes just like with any other kind of array.  Which in fact will simplify
your event handler code, because you won't need a temporary buffer anymore.
You can use the TIdBytes as-is:

    void __fastcall IdUDPServerUDPRead(TIdUDPListenerThread* AThread,
TIdBytes AData, TIdSocketHandle* ABinding)
    {
        try
        {
            // assuming Udata is large enoughto hold all of the bytes, of
course...
            memcpy(RxBuf->Udata, &AData[0], AData.Length);
        }
        //...
    }

> TIdBytes appears to be be a byte array wrapper, which
> doesn't seem the same as a TStream.

No, it is not the same.  If you look at the declaration of TIdBytes in
IdGlobal.hpp, you will see that it is a typedef for the VCL's DynamicArray
templated class:

    typedef DynamicArray<Byte> TIdBytes;

DynamicArray is documented in BCB's help files.


Gambit