🚀 go-pugleaf

"Martin" <dev@no.comppromed.spam.com> wrote in message
news:44285053$1@newsgroups.borland.com...

> I don't think I'm leaving anything in the input
> buffer. Here's the OnRead event:

You should be calling ReceiveLength() before calling ReceiveBuf()

    void __fastcall socketClass::onRead(TObject *Sender, TCustomWinSocket
*Socket)
    {
        char buf[ 4096];
        int numBytes;

        do
        {
            numBytes = Socket->ReceiveLength();
            if( numBytes > 0 )
                numBytes = Socket->ReceiveBuf(buf, min(sizeof(buf),
numBytes));

            if( numBytes < 1 )
                break;

            if( cfg.comDiag > 1 )
                audit( HERE, "%s %s:onRead - Recving %d bytes\n",
currentTime(), this->sktId,  numBytes);

            inBuf->writeData(buf, numBytes);
        }
        while( true );
    }

> inBuf is a ring buffer class that we wrote years ago. It stores the
> data until the app has a chance to get around to it (within 0.5 sec.).
> It's possible that the ring buffer is messing with me but it's been in
> use longer than the underlying socket stuff.

Are you sure that you are not filling the buffer beyond its capacity,
overriding the surrounding memory?

Did you verify that the sending application is actually sending its data
without errors?

Also, non-blocking sockets rely on the message queue, so are you blocking
the queue at any time from processing new messages?

Are there are firewalls or routers in between your application and the
sending application, which might be blocking the data?


Gambit