Lines Matching full:sockets

3 BSD Sockets
13 Zephyr offers an implementation of a subset of the BSD Sockets API (a part
17 Here are the key requirements and concepts which governed BSD Sockets
28 BSD Sockets compatible API is enabled using :kconfig:option:`CONFIG_NET_SOCKETS`
49 sockets). For example, a call ``recv(sock, 1000, 0)`` may return 100,
53 The BSD Sockets API uses file descriptors to represent sockets. File
55 among sockets, files, special devices (like stdin/stdout), etc. Internally,
57 The file descriptor table is used by the BSD Sockets API even if the rest
60 See :zephyr:code-sample:`sockets-echo-server` and :zephyr:code-sample:`sockets-echo-client`
66 Secure Sockets
70 and configure sockets with TLS protocol types, facilitating secure
72 mbedTLS library. Secure sockets implementation allows use of both TLS and DTLS
76 To enable secure sockets, set the :kconfig:option:`CONFIG_NET_SOCKETS_SOCKOPT_TLS`
86 secure sockets. See :c:func:`tls_credential_add` for more information.
141 Several samples in Zephyr use secure sockets for communication. For a sample use
142 see e.g. :zephyr:code-sample:`echo-server sample application <sockets-echo-server>` or
143 :zephyr:code-sample:`HTTP GET sample application <sockets-http-get>`.
145 Secure Sockets options  argument
148 Secure sockets offer the following options for socket management:
156 sockets). This allows for seamless integration for devices which provide an
224 the native TLS sockets.
226 for the remaining native sockets.
234 same type of sockets, are available. The same problem arises when both native
235 and offloaded sockets are available in the system.
262 Similarly, if TLS is supported by both native and offloaded sockets,
295 BSD Sockets