If I'm understanding your question, the tcp and udp appcalls can service different ports with a switch on uip_conn->lport. Basically demuxing service ports or client connected ports in a switch statement.
The appstate is hooked into uip in uipopt.h For example, for tcp: typedef struct httpd_state uip_tcp_appstate_t; And for udp: typedef struct udp_state uip_udp_appstate_t; Then httpd state can include whatever fields you wish to keep track of Various port conditions. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Glenn Jones Sent: Sunday, February 25, 2007 8:10 PM To: uip-users@sics.se Subject: [uip-users] Use resolv and dhcpc in the same uIP app? Use resolv and dhcpc in the same uIP app? What changes have to be made to use both resolv.c and dhcpc.c in the same application. From what I have read on this list, I see the need to maintain app states for both but I am not sure how to handle UIP_UDP_APPCALL in uip.c ? Has anybody else already done this? Glenn
