Lines Matching +full:in +full:- +full:application

26     :figclass: align-center
32 * **Network Application.** The network application can either use the provided
33   application-level protocol libraries or access the
35   connection, send or receive data, and close a connection. The application can
45   * Application-level network protocols like CoAP, LWM2M, and MQTT.
46     See :ref:`application protocols chapter <net_protocols>` for information
53   that is common in all the network interfaces, such as setting network
54   interface down, etc. There can be multiple network interfaces in the system.
68 * **Network Device Drivers.** The actual low-level device drivers handle the
74 An application typically consists of one or more :ref:`threads <threads_v2>`
75 that execute the application logic. When using the
79 .. figure:: zephyr_netstack_overview-rx_sequence.svg
81     :figclass: align-center
86 -------------------
91    data. The network packet is placed in the proper RX queue (implemented by
92    :ref:`k_fifo <fifos_v2>`). By default there is only one receive queue in
95    See :ref:`traffic-class-support` for more details. The receive queues also
96    act as a way to separate the data processing pipeline (bottom-half) as
97    the device driver is running in an interrupt context and it must do its
111    belongs and puts it in a queue for that socket, in order to separate the
112    networking code from the application. Typically the application is run in
113    userspace context and the network stack is run in kernel context.
115 7. The application will then receive the data and can process it as needed.
116    The application should have used the
121 .. figure:: zephyr_netstack_overview-tx_sequence.svg
123     :figclass: align-center
128 -----------------
130 1. The application should use the
133 2. The application data is prepared for sending to kernel space and then
136 3. Depending on the socket type, a protocol header is added in front of the
138    constructed and placed in front of the data.
148    one transmit queue in the system, but it is possible to have up to 8
150    priority. See :ref:`traffic-class-support` for more details.
159 Note that in both the TX and RX data paths, the queues
162 These :ref:`threads <threads_v2>` might run in different contexts