[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [lwip-users] tcp_connect: order of events

From: Tom C. Barker
Subject: RE: [lwip-users] tcp_connect: order of events
Date: Wed, 2 Mar 2005 11:26:45 -0800

What I was finding was a few second delay in getting the
first data to be sent. After the data came the ACK.
However, I have not been able to reproduce the problem
since I let my _poll and _sent functions handle data sending
in a little different way than I had first crafted.

When I changed the order, I would get an immediate ACK and
then get my data sent out via a my _poll function (and subsequent
packets sent out via my _sent function).


-----Original Message-----
From: address@hidden
[mailto:address@hidden Behalf
Of Kieran Mansley
Sent: Friday, February 25, 2005 12:23 PM
To: Mailing list for lwIP users
Subject: Re: [lwip-users] tcp_connect: order of events 

On Fri, 25 Feb 2005, Tom C. Barker wrote:
>      TCP_EVENT_CONNECTED(pcb, ERR_OK, err);
>      tcp_ack(pcb);
> Can I reverse this order so to have
>      tcp_ack(pcb);
>      TCP_EVENT_CONNECTED(pcb, ERR_OK, err);
> or will this cause a problem with the stack?

I don't think it will cause a problem, but I'm curious that this could 
ever make a difference.  What is the problem that you see?

Any data packets that get sent before the ACK will perform the function of 
the ACK - they have the ACK field in the TCP header set - and so the order 
should not matter.

Have you tried it the other way round and seen any difference?



lwip-users mailing list

reply via email to

[Prev in Thread] Current Thread [Next in Thread]