Lines Matching full:api
6 * @defgroup api APIs
17 * thread. The sequential API has a much higher overhead and is not very
29 * programs. In fact, the sequential API is implemented as an application
32 * Do not confuse the lwIP raw API with raw Ethernet or IP sockets.
37 * Raw API applications may never block since all packet processing
42 * @ingroup api
57 * The raw API (sometimes called native API) is an event-driven API designed
59 * receive. This API is also used by the core stack for interaction between
60 * the various protocols. It is the only API available when running lwIP
64 * @ingroup api
67 * The sequential API provides a way for ordinary, sequential, programs
68 * to use the lwIP stack. It is quite similar to the BSD socket API. The
74 * @defgroup socket Socket API
75 * @ingroup api
76 * BSD-style socket API.\n
80 * The socket API is a compatibility API for existing applications,
81 * currently it is built on top of the sequential API. It is meant to
82 * provide all functions needed to run socket API applications running
84 * in the specification of this API, there might be incompatibilities
107 * * Support TLS via new @ref altcp_api connection API (https, smtps, mqtt over TLS)
114 * * socket API: support poll(), sendmsg() and recvmsg(); fix problems on close
252 We can give you some idea on how to proceed when using the raw API.
315 * environment, raw API functions MUST only be called from the core thread
316 * since raw API functions are not protected from concurrent access (aside
318 * the sequential- or socket API communicate with this main thread through
323 * from these API header files are thread-safe:
324 * - api.h
337 * Netconn or Socket API functions are thread safe against the