🚀 go-pugleaf

Gosh you worry too much, Hans. Socket->ReceiveLength() returns the maximum bytes
the receive buffer can hold, if filled up. Subsequent calls return that amount
or less. The last time it will return the remaining bytes, which may be less
than the initial return value. I am sure this code is safe when using Winsock or
Winsock2.
-- 
Mark Jacobs

"Hans Galema" <dontusethis@dontusethis.nl> wrote in message
news:41595d75@newsgroups.borland.com...
| Byanex wrote:
|
| > Mark Jacobs
| >
| > Thank you very much, that code realy works.
|
| That is difficult to believe.
|
|  > | void __fastcall TForm1::ClientSocket1Read(TObject *Sender,
|  > |       TCustomWinSocket *Socket)
|  > | {
|  > |     TMemoryStream *pms=new TMemoryStream();
|  > |     int count=Socket->ReceiveLength();
|  > |     char *Buf=new char[count+9];
|  > |     while (count>0)
|  > |     {
|  > |        Socket->ReceiveBuf(Buf,count); pms->Write(Buf,count);
|  > |        count=Socket->ReceiveLength();
|  > |     }
|  > |     delete Buf; pms->Position=0;
|  > |     Image1->Picture->Bitmap->LoadFromStream(pms);
|  > |     delete pms;
|  > | }
|
| Maybe it works for very small bitmaps. But did you try bitmaps
| with size > 100 KB ?
|
| If you have a large bitmap then ClientSocket1Read() will
| be triggered many times if you just read the bytes
| indicated by ReceiveLength().
|
| In the loop you call ReceiveLength() more often but the same buffer
| for the old Length() is used.
|
| ReceiveLength() in the loop could as well return 0, then you would
| stop for an incomplete image. The rest would then come with a next
| call of ClientSocket1Read.

If it returned 0, then the transaction is complete. Remember, the actual number
of bytes received is the return value of ReceiveBuf.

|
| I did not test this code. I only have my doubts that it will behave
| as expected.