🚀 go-pugleaf

"Eyyub Volkan �ektimur" <evcektimur@prokon.com.tr> wrote in message
news:41f8bc22@newsgroups.borland.com...

>
WritenBytes+=SocketStream->Write((WriteMemory+(int)WritenBytes),DataSize-Wri
> tenBytes);

You are not taking into account that Write() can return a negative value,
thus your WrittenBytes value can become out-of-sync.  You should do the
following instead:

    DWORD TotalBytes = 0;

    while( TotalBytes != DataSize ...)
    {
        WritenBytes = SocketStream->Write(&WriteMemory[TotalBytes],
DataSize-TotalBytes);
        if( WrittenBytes < 0 )
        {
            // socket error
            break;
        }
        if( WritenBytes == 0 )
        {
            // wait a moment and try again
            Sleep(250);
        }
        else
        {
            TotalBytes += WritenBytes;
            // no need to sleep here
        }
    }

Alternatively:

    char *WriteMemory = ...;

    while( DataSize > 0 ...)
    {
        WritenBytes = SocketStream->Write(WriteMemory, DataSize);
        if( WrittenBytes < 0 )
        {
            // socket error
            break;
        }
        if( WritenBytes == 0 )
        {
            // wait a moment and try again
            Sleep(250);
        }
        else
        {
            DataSize -= WritenBytes;
            WriteMemory += WritenBytes;
            // no need to sleep here
        }
    }

> when Write method returns smaller than DataSize (especially 0) , and the
> package re-writen , client side reads this package twice , supposing that
> server side writen this package twice

That is possible.  You did not specify what your TWinSocketStream timeouts
are set to.  If they are too small, Write() could be returning earlier than
the data is actually sent, but the data could still be sent afterwords since
Write() does not cancel the send before exiting.  TWinSocketStream uses
overlapped I/O on the socket.  When Write() times out, it returns 0
immediately, but the overlapped operation is still in progress.  If you set
your timeouts higher, there is less chance of Write() exiting prematurely
before the data is actually sent.


Gambit