Lines Matching full:api

7 * low-level "core" / "callback" or "raw" API.
8 * higher-level "sequential" API.
9 * BSD-style socket API.
11 The raw API (sometimes called native API) is an event-driven API designed
13 receive. This API is also used by the core stack for interaction between
14 the various protocols. It is the only API available when running lwIP
17 The sequential API provides a way for ordinary, sequential, programs
18 to use the lwIP stack. It is quite similar to the BSD socket API. The
24 The socket API is a compatibility API for existing applications,
25 currently it is built on top of the sequential API. It is meant to
26 provide all functions needed to run socket API applications running
28 in the specification of this API, there might be incompatibilities
37 environment, raw API functions MUST only be called from the core thread
38 since raw API functions are not protected from concurrent access (aside
40 the sequential- or socket API communicate with this main thread through
45       from these API header files are thread-safe:
46       - api.h
59       Netconn or Socket API functions are thread safe against the
72 ** The remainder of this document discusses the "raw" API. **
78 thread. The sequential API has a much higher overhead and is not very
90 programs. In fact, the sequential API is implemented as an application
93 Do not confuse the lwIP raw API with raw Ethernet or IP sockets.
98 Raw API applications may never block since all packet processing
130 the sequential API and of the BSD socket API. A new TCP connection
380 We can give you some idea on how to proceed when using the raw API.
484 To achieve zero-copy on transmit, the data passed to the raw API must
489 This implies that PBUF_RAM/PBUF_POOL pbufs passed to raw-API send functions