Appication specific configurations
[Configuration options for uIP]


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 size of the application structure with the UIP_APPSTATE_SIZE macro.

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 {
  u8_t state; 
  u16_t count;
  char *dataptr;
  char *script;
};
#define UIP_APPSTATE_SIZE (sizeof(struct httpd_state))


Defines

#define UIP_APPCALL()
#define UIP_APPSTATE_SIZE   0
#define UIP_APPCALL   example5_app
#define UIP_APPSTATE_SIZE   0


Define Documentation

#define UIP_APPCALL   example5_app
 

Definition at line 544 of file linux/uipopt.h.

 
define UIP_APPCALL  ) 
 

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

Definition at line 553 of file avr/uipopt.h.

Referenced by uip_process().

#define UIP_APPSTATE_SIZE   0
 

Definition at line 551 of file linux/uipopt.h.

define UIP_APPSTATE_SIZE   0
 

The size of the application state that is to be stored in the uip_conn structure.

Definition at line 560 of file avr/uipopt.h.


Generated on Fri Jan 6 22:23:18 2006 for EtherProgs by  doxygen 1.4.5