🚀 go-pugleaf

Hans Galema wrote:
> Joe Black wrote:
> 
>> .... The problem seems to be when I send several packets straight 
>> after each other, the packets are all sent within a thread that 
>> activates every 35 ms and it sends one packet at a time.
> 
> 
> But what is the problem ?

Several packets get concatenated together.

> 
>> For some reason though several packets seem to get concatenated 
>> together to form one larger packet, if I slow down the transmit thread 
>> to say every 200ms this problems dissapears, 
> 
> 
> Yes that is normal. Winsock will send it's buffer when it is full or
> a certain amount of time has elapsed.

This is what I was wondering, I was hoping I could send data when it was 
empty.

> 
>> this sort of time delay however is unacceptable. What I would like to 
>> know is:
>>
>> Is there anyway to determine whether the last packet was sent before I 
>> attempt to send the next one 
> 
> 
> Don't think so. But why would you? You have to program the receiving
> side in such a way that it can handle multiple 'packets' in one read event.
> Just as the receiving side should concatenate read-events until
> a complete (big) message is received.

I have a fairly simple app and I was hoping to make it easier, if this 
is the way to do it then I will code it to as you suggest.

> 
> FYI: it is confusing that you use the word packet for the message
> that you send. TCP/IP uses packets already.

Appologies, the data I send is in a packet format, hence i use the term 
packet. I am fairly new to the Sockets side of things so my terminology 
may be confusing.

> 
> Hans.

Many thanks, you seem to have answered everything I needed to know

Joe