Searched refs:client (Results 251 – 275 of 326) sorted by relevance
1...<<11121314
/Zephyr-latest/doc/services/device_mgmt/ |
D | ota.rst | 77 connect to an LwM2M server using DTLS. A :zephyr:code-sample:`lwm2m-client` sample is
|
/Zephyr-latest/boards/shields/atmel_rf2xx/doc/ |
D | index.rst | 282 and Echo client samples, which provide out-of-the-box configuration for 287 :zephyr:code-sample:`sockets-echo-client` samples for details.
|
/Zephyr-latest/doc/releases/ |
D | release-notes-1.13.rst | 188 * Port native API echo-server/echo-client samples to BSD sockets API, with 190 * Handle out-of-buf situations gracefully in echo-client and echo-server sample 211 - Generic OnOff client and server. 212 - Generic Level client and server. 213 - Generic Power OnOff client and server. 214 - Light Lightness client and server. 215 - Light CTL client and server. 300 * :github:`9746` - zephyr networking non socket client server, qemu_x86 issue 449 * :github:`8888` - http client example fails on mimxrt1050_evk 607 * :github:`7553` - DHCP client does not notice missing link
|
D | release-notes-1.9.rst | 117 by applications to create client/server applications with transparent 130 * Improvements to HTTP server and client libraries 243 * ``ZEP-2116`` - Common API for networked apps to create client/server applications 376 * ``ZEP-2561`` - samples/net: The HTTP client failed to send the POST request
|
D | release-notes-1.10.rst | 107 * SNTP (Simple Network Time Protocol) client library added. 375 * :github:`4058` - samples/net/http_client: The HTTP client failed to send the GET request 386 * :github:`4188` - samples /net/echo_server:failed to send packets to client 393 * :github:`4258` - samples/net/zoap_server : unable to communicate between zoap client and server 417 * :github:`4424` - Turning on network debug message w/ LwM2M sample client will result in stack che… 466 * :github:`4738` - ble-mesh: proxy.c : Is clients-> conn a clerical error? it should be client-> co…
|
/Zephyr-latest/doc/develop/debug/ |
D | index.rst | 97 GDB client 157 As configured above, when you connect the GDB client, the application will be 165 :command:`continue` after connecting the client, the application will run,
|
/Zephyr-latest/subsys/mgmt/updatehub/ |
D | Kconfig | 81 client and the server
|
/Zephyr-latest/subsys/bluetooth/ |
D | Kconfig.iso | 16 # TODO: Split between client (central) and server (peripheral)
|
/Zephyr-latest/doc/connectivity/bluetooth/shell/audio/ |
D | bap_broadcast_assistant.rst | 30 bap_broadcast_assistant - Bluetooth BAP broadcast assistant client shell
|
/Zephyr-latest/samples/drivers/ethernet/eth_ivshmem/ |
D | README.rst | 142 # Connect iPerf TCP client
|
/Zephyr-latest/samples/net/dns_resolve/ |
D | README.rst | 55 are the IPv6 addresses for the DNS client running Zephyr and the DNS server,
|
/Zephyr-latest/doc/services/device_mgmt/smp_groups/ |
D | smp_group_3.rst | 25 the original upstream version, however, the original client functionality should work for 121 | | cannot be specified through this and must be known by the client. |
|
D | smp_group_8.rst | 53 path supplied by the client. 165 of a file and it is client side responsibility to track progress of upload. 191 path supplied by the client.
|
/Zephyr-latest/doc/connectivity/networking/ |
D | qemu_setup.rst | 220 This will start QEMU, waiting for a connection from a client QEMU. 230 :build-args: client
|
/Zephyr-latest/subsys/net/lib/sockets/ |
D | Kconfig | 148 This is mostly useful for TLS client side to tell TLS server what is 165 freed. This is needed to prevent situation when DTLS client shuts down 235 int "Maximum number of stored client TLS/DTLS sessions"
|
/Zephyr-latest/subsys/mgmt/mcumgr/smp/ |
D | Kconfig | 150 client.
|
/Zephyr-latest/samples/net/sockets/big_http_download/ |
D | README.rst | 11 a simple HTTP GET client using a BSD Sockets compatible API. Unlike
|
/Zephyr-latest/samples/net/cloud/aws_iot_mqtt/src/ |
D | main.c | 202 static void mqtt_event_cb(struct mqtt_client *client, const struct mqtt_evt *evt) in mqtt_event_cb() argument
|
/Zephyr-latest/samples/boards/nordic/mesh/onoff_level_lighting_vnd_app/ |
D | README.rst | 108 The meshctl utility also supports a onoff model client that can be used to
|
/Zephyr-latest/doc/connectivity/bluetooth/api/mesh/ |
D | blob.rst | 144 can retrieve the capabilities of each BLOB Transfer Server before starting the transfer. The client 174 The timeout of the BLOB transfer is based on a Timeout Base value. Both client and server use the
|
D | rpr_cli.rst | 60 procedure completes, the server sends the scan report that will be handled in the client's
|
/Zephyr-latest/tests/net/lib/lwm2m/lwm2m_rd_client/src/ |
D | main.c | 62 static void lwm2m_event_cb(struct lwm2m_ctx *client, enum lwm2m_rd_client_event client_event) in lwm2m_event_cb() argument 64 ARG_UNUSED(client); in lwm2m_event_cb()
|
/Zephyr-latest/doc/services/shell/ |
D | index.rst | 65 as a shell backend. Connecting to it can be done using PuTTY or any ``telnet`` client. 72 By default the telnet client won't handle telnet commands and configuration. Although 74 This will give the telnet client access to a very limited set of supported commands but 76 option. This will allow the client to be in character mode (character at a time), 77 similar to a UART backend in that regard. This will make the client send a character
|
/Zephyr-latest/doc/connectivity/networking/api/ |
D | sockets.rst | 60 See :zephyr:code-sample:`sockets-echo-server` and :zephyr:code-sample:`sockets-echo-client` 61 sample applications to learn how to create a simple server or client BSD socket based
|
/Zephyr-latest/subsys/bluetooth/mesh/ |
D | Kconfig | 879 Enable support for the configuration client model. 887 This timeout controls how long config client waits for a response 896 Enable support for the health client model. 904 This timeout controls how long health client waits for a response 987 Controls the number of times the client will attempt to resend missing 1213 Enable support for the SAR configuration client model. 1365 This timeout controls how long the bridge configuration client waits for a 1419 the proxy client. This value is application specific and should be large 1420 enough so that proxy client can communicate with several devices through 1426 bool "Proxy client support"
|
1...<<11121314