🚀 go-pugleaf

"Eric Patterson" <eric.patterson@bepco.com> wrote in message
news:4443dd4e@newsgroups.borland.com...

> After thinking a minute, what about this:
<snip>
> That way it will continue to send until no more length is detected.

No, because you are re-sending the entire string contents every time, even
for portions of it that are successfully sent in previous loop iterations.
Youare not adjusting the sending to send only the characters that are
actually pending.

A more accurate approach is as follows:

    TCustomWinSocket *Socket =
Server->ServerSocket1->Socket->Connections[ii];
    AnsiString temp = AMsg + "\n";
    int len;

    while( temp.Length() > 0 )
    {
        len = Socket->SendText(temp);
        if( len > 0 )
        {
            temp = temp.SubString(len+1, MaxInt);
            continue;
        }

        if( (len == -1) && (WSAGetLastError() == WSAEWOULDBLOCK) )
        {
            Sleep(10);
            continue;
        }

        break;
    }

Alternatively:

    TCustomWinSocket *Socket =
Server->ServerSocket1->Socket->Connections[ii];
    AnsiString temp = AMsg + "\n";
    int sent, len = temp.Length();
    char *ptr = temp.c_str();

    while( len > 0 )
    {
        sent = Socket->SendBuf(ptr, len);
        if( sent > 0 )
        {
            ptr += sent;
            len -= sent;
            continue;
        }

        if( (sent == -1) && (WSAGetLastError() == WSAEWOULDBLOCK) )
        {
            Sleep(10);
            continue;
        }

        break;
    }


> I figure if a negative is returned then the OnError event should catch it.

SendText/Buf() will still return the negative value regardless of whether
the OnError event is used.  All the OnError event can do is choose whether
to stop the error from throwing an exception or not.


Gambit