🚀 go-pugleaf

"qyte" <gyte@vivodinet.gr> wrote in message
news:42279c95@newsgroups.borland.com...

> The Problem is that when i call SendBuf i want to
> know for sure if the data will be sent.

There is no way to determine that.  SendBuf() simply passes the data to the
socket, which buffers the data internally for later transmission.  There is
no way to know whether the socket will actually send the data.  All that is
returned to you is whether the socket accepted the data, but there is no way
to know what the socket actually does with the data.  Once the socket
accepts the data, it is out of your hands.

> I want to add an abort

The only way to abort a socket is to disconnect it.  Once the socket has
accepted the data, you cannot tell the socket later to ignore the data it
already accepted.

> even if i close the timer there is still some data on the winsock
> that will be sent in the future and of course when the receiver
> takes them and calls fwrite then an access violation accurrs.

Why would there be an AV?  Because you are writing to a closed file?  That
is your own responsibilty to keep track of in the first place.  Simply don't
write to files you have already closed.  Just discard the extra data.

> So i want to know when all the data will have gone

There is no way to know that.

> i know that i can call sendbuf like that:
>
> while(sendbuf(a,packet)<0);
>
> just to be certain that the data was sent. but there is no guarentee
> that the whole packet will be sent.

You need to examine the actual return value of SendBuf() to know how much
data was accepted by the socket.  If less then the original packet size then
you will have to re-send the remaining bytes in another call to SendBuf(),
repeating as needed until the packet has been passed to the socket in full.


Gambit