Lines Matching full:application

5 lwIP provides three Application Program's Interfaces (APIs) for programs
21 code and the application program must reside in different execution
39 from pbuf- and memory management functions). Application threads using
74 The raw TCP/IP interface allows the application program to integrate
77 code. The TCP/IP code and the application program both run in the same
80 on the application.
84 development is somewhat harder and application programs written for
89 All APIs can be used simultaneously by different application
90 programs. In fact, the sequential API is implemented as an application
105 invoked by the lwIP core when activity related to that application
106 occurs. A particular application may register to be notified via a
109 closed, etc. An application can provide a callback function to perform
117 The function for setting the application connection state is:
207 host, the application will be notified with a call to a specified
232   the application should wait until some of the currently enqueued
247 TCP data reception is callback based - an application specified
249 application has taken the data, it has to call the tcp_recved()
266   Must be called when the application has received the data. The len
270 --- Application polling
273 received), lwIP will repeatedly poll the application by calling a
278 the application may use the polling functionality to call tcp_write()
286   be called to poll the application. The interval is specified in
288   twice a second. An interval of 10 means that the application would
297   was available for closing the connection. If so, the application
314 If a connection is aborted because of an error, the application is
474 to match your application and network.
490 must *not* be reused by the application unless their ref-count is 1.