🚀 go-pugleaf

Just had some time to try rebuilding Indy 10 again, and just want to clarify 
the new event handler parameters for IdUDPServer.  Got most things compiled 
now and just the following to ask.

The IdUDPServer class has the following read event:
    TUDPReadEvent = procedure (Sender: TObject; AData: TIdBytes; ABinding: 
TIdSocketHandle) of object;

So from Indy 9 to 10:
    void __fastcall IdUDPServerUDPRead(TObject *Sender,TStream 
*AData,TIdSocketHandle *ABinding);
to
    void __fastcall IdUDPServerUDPRead(TIdUDPListenerThread* AThread, 
TIdBytes AData, TIdSocketHandle* ABinding);

In my Indy9 read event handler it looks like the following, the read event 
handler reads data from the stream until there is nothing more to read, exit 
loop, then process whats been received.  What I want to know is how this 
changes with Indy 10 and the TIdBytes parameter?  TIdBytes appears to be be 
a byte array wrapper, which doesn't seem the same as a TStream.

Regards,

Paul
----

    try
    {
        int BufSize = AData->Size;
        int BufIndx = 0;
        char * Buf  = RxBuf->Udata;
        bool result = false;

        while (BufSize > 0)
        {
            int iRead = 0;

            iRead = AData->Read( &Buf[BufIndx], BufSize );

            if( iRead > 0 )
            {
                // success
                BufIndx += iRead;
                BufSize -= iRead;
                result = true;
            }
            else
            {
                // fail
                BufSize = 0;
            }
        }