Application specific configurations

Collaboration diagram for Application specific configurations:

Macros
#define	UIP_APPCALL   tcpip_uipcall

Typedefs
typedef struct tcpip_uipstate	uip_tcp_appstate_t
typedef struct tcpip_uipstate	uip_udp_appstate_t

Detailed Description

An uIP application is implemented using a single application function that is called by uIP whenever a TCP/IP event occurs. The name of this function must be registered with uIP at compile time using the UIP_APPCALL definition.

uIP applications can store the application state within the uip_conn structure by specifying the type of the application structure by typedef:ing the type uip_tcp_appstate_t and uip_udp_appstate_t.

The file containing the definitions must be included in the uipopt.h file.

The following example illustrates how this can look.

void httpd_appcall(void);
#define UIP_APPCALL     httpd_appcall

struct httpd_state {
uint8_t state;
uint16_t count;
char *dataptr;
char *script;
};
typedef struct httpd_state uip_tcp_appstate_t

Macro Definition Documentation

define UIP_APPCALL   tcpip_uipcall

The name of the application function that uIP should call in response to TCP/IP events.

Definition at line 79 of file tcpip.h.

Referenced by uip_process().

Typedef Documentation

typedef uip_tcp_appstate_t

The type of the application state that is to be stored in the uip_conn structure. This usually is typedef:ed to a struct holding application state information.

Definition at line 86 of file tcpip.h.

typedef uip_udp_appstate_t

The type of the application state that is to be stored in the uip_conn structure. This usually is typedef:ed to a struct holding application state information.

Definition at line 85 of file tcpip.h.