Important changes to repositories hosted on mbed.com
Mbed hosted mercurial repositories are deprecated and are due to be permanently deleted in July 2026.
To keep a copy of this software download the repository Zip archive or clone locally using Mercurial.
It is also possible to export all your personal repositories from the account settings page.
Dependents: TYBLE16_simple_data_logger TYBLE16_MP3_Air
Non thread-safe APIs, callback style for maximum performance and minimum memory footprint. More...
Modules | |
| Application layered TCP Introduction | |
Overview -------- altcp (application layered TCP connection API; to be used from TCPIP thread) is an abstraction layer that prevents applications linking hard against the tcp::h functions while providing the same functionality. | |
| DNS | |
Implements a DNS host name to IP address resolver. | |
| IP | |
| Network interface (NETIF) | |
| RAW | |
Implementation of raw protocol PCBs for low-level handling of different types of protocols besides (or overriding) those already available in lwIP. | |
| TCP | |
Transmission Control Protocol for IP | |
| UDP | |
User Datagram Protocol module | |
| Ethernet | |
Detailed Description
Non thread-safe APIs, callback style for maximum performance and minimum memory footprint.
Program execution is driven by callbacks functions, which are then invoked by the lwIP core when activity related to that application occurs. A particular application may register to be notified via a callback function for events such as incoming data available, outgoing data sent, error notifications, poll timer expiration, connection closed, etc. An application can provide a callback function to perform processing for any or all of these events. Each callback is an ordinary C function that is called from within the TCP/IP code. Every callback function is passed the current TCP or UDP connection state as an argument. Also, in order to be able to keep program specific state, the callback functions are called with a program specified argument that is independent of the TCP/IP state. The raw API (sometimes called native API) is an event-driven API designed to be used without an operating system that implements zero-copy send and receive. This API is also used by the core stack for interaction between the various protocols. It is the only API available when running lwIP without an operating system.
Generated on Tue Jul 12 2022 13:55:22 by
1.7.2