[lwip-users] TCP_EVENT_CONNECTED: call ordering

[Tom C. Barker]

Hello,

In setting up an SMTP client, I have found that if I send a message 
upon callback ( TCP_EVENT_CONNECTED ) I get the following out-of-order
trace where the ACK in 4 should be before the first data (HELO) I send.

  Protocol Info
1 TCP      4097 > smtp [SYN] Seq=6519 Ack=0 Win=2048 Len=0
2 TCP      smtp > 4097 [SYN, ACK] Seq=695488828 Ack=6520 Win=16560 Len=0
3 SMTP     Message
4 TCP      smtp > 4097 [ACK] Seq=695488829 Ack=6524 Win=16556 Len=0
5 SMTP     Response: 220 la.te.da.com ESMTP MyPoint 3.3.8-GR; Fri, 16 Jan
2004 09:50:32 -0800  
6 TCP      4097 > smtp [ACK] Seq=6524 Ack=695488914 Win=1963 Len=0

This behavior is confirmed in TCPIN.C:

      /* Call the user specified function to call when successfully
connected. */
      TCP_EVENT_CONNECTED(pcb, ERR_OK, err);
      tcp_ack(pcb);

We perform pcb->connnected and THEN ack. Certainly I can reverse the two,
but would
I be breaking anything that anyone knows of? Any of you lwip vets care to
share
your wisdom on this? 

Thanks in advance,
Tom