| /third_party/libcoap/doc/ |
| D | main.md | 4 A C implementation of the Constrained Application Protocol (RFC 7252)
25 * [RFC7252: The Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7252)
27 * [RFC7390: Group Communication for the Constrained Application Protocol (CoAP)](https://rfc-editor…
29 * [RFC7641: Observing Resources in the Constrained Application Protocol (CoAP)](https://rfc-editor.…
31 * [RFC7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)](https://rfc-editor…
33 * [RFC7967: Constrained Application Protocol (CoAP) Option for No Server Response](https://rfc-edit…
35 * [RFC8132: PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)](https://rfc-ed…
37 * [RFC8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets](https://rfc-edit…
39 * [RFC8516: "Too Many Requests" Response Code for the Constrained Application Protocol](https://rfc…
43 * [RFC8768: Constrained Application Protocol (CoAP) Hop-Limit Option](https://rfc-editor.org/rfc/rf…
[all …]
|
| /third_party/rust/crates/rustix/tests/net/ |
| D | connect_bind_send.rs | 2 AddressFamily, Ipv6Addr, Protocol, RecvFlags, SendFlags, SocketAddrAny, SocketAddrV4,
13 rustix::net::socket(AddressFamily::INET, SocketType::STREAM, Protocol::default())?; in net_v4_connect_any()
18 let sender = rustix::net::socket(AddressFamily::INET, SocketType::STREAM, Protocol::default())?; in net_v4_connect_any()
47 Protocol::default(), in net_v6_connect_any()
56 Protocol::default(), in net_v6_connect_any()
84 rustix::net::socket(AddressFamily::INET, SocketType::STREAM, Protocol::default())?; in net_v4_connect()
93 let sender = rustix::net::socket(AddressFamily::INET, SocketType::STREAM, Protocol::default())?; in net_v4_connect()
122 Protocol::default(), in net_v6_connect()
135 Protocol::default(), in net_v6_connect()
163 rustix::net::socket(AddressFamily::INET, SocketType::STREAM, Protocol::default())?; in net_v4_bind_any()
[all …]
|
| D | unix.rs | 19 accept, bind_unix, connect_unix, listen, socket, AddressFamily, Protocol, SocketAddrUnix,
34 Protocol::default(), in server()
88 Protocol::default(), in client()
108 Protocol::default(), in client()
|
| D | v4.rs | 9 Protocol, RecvFlags, SendFlags, SocketAddrAny, SocketAddrV4, SocketType,
18 socket(AddressFamily::INET, SocketType::STREAM, Protocol::default()).unwrap(); in server()
58 let data_socket = socket(AddressFamily::INET, SocketType::STREAM, Protocol::default()).unwrap(); in client()
|
| D | v6.rs | 9 Protocol, RecvFlags, SendFlags, SocketAddrAny, SocketAddrV6, SocketType,
20 Protocol::default(), in server()
65 Protocol::default(), in client()
|
| /third_party/libcoap/man/ |
| D | coap.txt.in | 57 "https://rfc-editor.org/rfc/rfc7252[RFC7252: The Constrained Application Protocol (CoAP)]"
59 …itor.org/rfc/rfc7390[RFC7390: Group Communication for the Constrained Application Protocol (CoAP)]"
61 …ditor.org/rfc/rfc7641[RFC7641: Observing Resources in the Constrained Application Protocol (CoAP)]"
63 …itor.org/rfc/rfc7959[RFC7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)]"
65 "https://rfc-editor.org/rfc/rfc7967[RFC7967: Constrained Application Protocol (CoAP) Option for No …
67 ….org/rfc/rfc8132[RFC8132: PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)]"
69 "https://rfc-editor.org/rfc/rfc8323[RFC8323: CoAP (Constrained Application Protocol) over TCP, TLS,…
71 …g/rfc/rfc8516[RFC8516: "Too Many Requests" Response Code for the Constrained Application Protocol]"
75 "https://rfc-editor.org/rfc/rfc8768[RFC8768: Constrained Application Protocol (CoAP) Hop-Limit Opti…
77 …974[RFC8974: Extended Tokens and Stateless Clients in the Constrained Application Protocol (CoAP)]"
[all …]
|
| /third_party/libcoap/ |
| D | README.md | 1 # libcoap: A C implementation of the Constrained Application Protocol (RFC 7252)
42 * [RFC7252: The Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7252)
44 * [RFC7390: Group Communication for the Constrained Application Protocol (CoAP)](https://rfc-editor…
46 * [RFC7641: Observing Resources in the Constrained Application Protocol (CoAP)](https://rfc-editor.…
48 * [RFC7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)](https://rfc-editor…
50 * [RFC7967: Constrained Application Protocol (CoAP) Option for No Server Response](https://rfc-edit…
52 * [RFC8132: PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)](https://rfc-ed…
54 * [RFC8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets](https://rfc-edit…
56 * [RFC8516: "Too Many Requests" Response Code for the Constrained Application Protocol](https://rfc…
60 * [RFC8768: Constrained Application Protocol (CoAP) Hop-Limit Option](https://rfc-editor.org/rfc/rf…
[all …]
|
| D | README | 1 # libcoap: A C implementation of the Constrained Application Protocol (RFC 7252)
42 * [RFC7252: The Constrained Application Protocol (CoAP)](https://rfc-editor.org/rfc/rfc7252)
44 * [RFC7390: Group Communication for the Constrained Application Protocol (CoAP)](https://rfc-editor…
46 * [RFC7641: Observing Resources in the Constrained Application Protocol (CoAP)](https://rfc-editor.…
48 * [RFC7959: Block-Wise Transfers in the Constrained Application Protocol (CoAP)](https://rfc-editor…
50 * [RFC7967: Constrained Application Protocol (CoAP) Option for No Server Response](https://rfc-edit…
52 * [RFC8132: PATCH and FETCH Methods for the Constrained Application Protocol (CoAP)](https://rfc-ed…
54 * [RFC8323: CoAP (Constrained Application Protocol) over TCP, TLS, and WebSockets](https://rfc-edit…
56 * [RFC8516: "Too Many Requests" Response Code for the Constrained Application Protocol](https://rfc…
60 * [RFC8768: Constrained Application Protocol (CoAP) Hop-Limit Option](https://rfc-editor.org/rfc/rf…
[all …]
|
| /third_party/mbedtls/scripts/mbedtls_dev/ |
| D | typing_util.py | 29 from typing_extensions import Protocol #pylint: disable=import-error
31 class Protocol: #type: ignore class
35 class Writable(Protocol):
|
| /third_party/protobuf/docs/ |
| D | third_party.md | 1 # Third-Party Add-ons for Protocol Buffers
3 This page lists code related to Protocol Buffers which is developed and maintained by third parties…
9 These are projects we know about implementing Protocol Buffers for other programming languages:
107 …Protocol Buffers. There are other third-party RPC implementations as well. Some of these actually…
146 There are miscellaneous other things you may find useful as a Protocol Buffers developer.
170 * [RSpec matchers and Cucumber step defs for testing Protocol Buffers](https://github.com/connamara…
171 * [Sbt plugin for Protocol Buffers](https://github.com/Atry/sbt-cppp)
174 * [Python scripts to convert between Protocol Buffers and JSON](https://github.com/NextTuesday/py-p…
175 * [Visual Studio Language Service support for Protocol Buffers](http://visualstudiogallery.msdn.mic…
176 * [Visual Studio Code Support for Protocol Buffers](https://marketplace.visualstudio.com/items?item…
[all …]
|
| /third_party/python/Lib/importlib/metadata/ |
| D | _meta.py | 1 from typing import Any, Dict, Iterator, List, Protocol, TypeVar, Union
7 class PackageMetadata(Protocol):
32 class SimplePath(Protocol):
|
| /third_party/protobuf/python/docs/ |
| D | index.rst | 1 .. Protocol Buffers documentation master file, created by
12 the `Protocol Buffers package for Python
18 Protocol Buffers Python API Reference
21 The complete documentation for Protocol Buffers is available via the web at:
|
| /third_party/protobuf/conformance/ |
| D | README.md | 1 Protocol Buffers - Google's data interchange format
7 correctness of Protocol Buffers implementations. These tests are designed
8 to be easy to run against any Protocol Buffers implementation.
54 Testing other Protocol Buffer implementations
57 To run these tests against a new Protocol Buffers implementation, write a
|
| /third_party/lwip/ |
| D | README | 16 * IP (Internet Protocol, IPv4 and IPv6) including packet forwarding over
18 * ICMP (Internet Control Message Protocol) for network maintenance and debugging
19 * IGMP (Internet Group Management Protocol) for multicast traffic management
26 * UDP (User Datagram Protocol) including experimental UDP-lite extensions
27 * TCP (Transmission Control Protocol) with congestion control, RTT estimation
41 * SNMPv2c agent with MIB compiler (Simple Network Management Protocol), v3 via altcp
|
| D | README_en.md | 16 * IP (Internet Protocol, IPv4 and IPv6) including packet forwarding over
18 * ICMP (Internet Control Message Protocol) for network maintenance and debugging
19 * IGMP (Internet Group Management Protocol) for multicast traffic management
26 * UDP (User Datagram Protocol) including experimental UDP-lite extensions
27 * TCP (Transmission Control Protocol) with congestion control, RTT estimation
41 * SNMPv2c agent with MIB compiler (Simple Network Management Protocol), v3 via altcp
|
| /third_party/protobuf/examples/ |
| D | README.md | 1 # Protocol Buffers - Code Example
3 This directory contains example code that uses Protocol Buffers to manage an
11 These examples are part of the Protocol Buffers tutorial, located at:
101 First, install the Protocol Buffers compiler (protoc).
103 Then, install the Go Protocol Buffers plugin ($GOPATH/bin must be in your $PATH
128 First, follow the instructions in [../README.md](../README.md) to install the Protocol Buffer Compi…
130 Then, install the Dart Protocol Buffer plugin as described [here](https://github.com/dart-lang/dart…
|
| /third_party/protobuf/js/ |
| D | README.md | 1 Protocol Buffers - Google's data interchange format
8 This directory contains the JavaScript Protocol Buffers runtime library.
19 To use Protocol Buffers with JavaScript, you need two main components:
25 2. The Protocol Compiler `protoc`. This translates `.proto` files
35 First, obtain the Protocol Compiler. The easiest way is to download
58 Using Protocol Buffers in your own project
61 To use Protocol Buffers in your own project, you need to integrate
62 the Protocol Compiler into your build system. The details are a
|
| /third_party/protobuf/src/ |
| D | README.md | 1 Protocol Buffers - Google's data interchange format
48 To build and install the C++ Protocol Buffer runtime and the Protocol
81 To compile a package that uses Protocol Buffers, you need to pass
83 Protocol Buffers integrates with pkg-config to manage this. If you
97 Note that packages written prior to the 2.2.0 release of Protocol
109 If you are writing an autoconf-based package that uses Protocol
216 Protocol Buffers C++ runtime libraries will have compatible ABIs.
229 The complete documentation for Protocol Buffers is available via the
|
| /third_party/protobuf/ruby/ |
| D | README.md | 1 This directory contains the Ruby extension that implements Protocol Buffers
12 In Gemfile (Please check a version of Protocol Buffers you needed [RubyGems](https://rubygems.org/g…
23 also want to install Protocol Buffers itself, as described in this repository's
92 We are using a version number scheme that is a hybrid of Protocol Buffers'
98 * First, we determine the prefix: a Protocol Buffers version "3.0.0-alpha-2"
|
| /third_party/python/Lib/test/ |
| D | test_typing.py | 15 from typing import Generic, ClassVar, Final, final, Protocol
772 class Coordinate(Protocol):
777 class Point(Coordinate, Protocol):
785 class XAxis(Protocol):
788 class YAxis(Protocol):
792 class Position(XAxis, YAxis, Protocol):
796 class Proto(Protocol):
816 class HasCallProtocol(Protocol):
823 class P(Protocol):
845 class Empty(Protocol):
[all …]
|
| /third_party/rust/crates/rustix/src/net/ |
| D | socketpair.rs | 2 use crate::net::{AddressFamily, Protocol, SocketFlags, SocketType};
18 protocol: Protocol, in socketpair() argument
|
| /third_party/python/Doc/library/ |
| D | errno.rst | 273 Protocol driver not attached
383 Protocol error
483 Protocol wrong type for socket
488 Protocol not available
493 Protocol not supported
508 Protocol family not supported
|
| /third_party/rust/crates/rustix/tests/io/ |
| D | epoll.rs | 7 accept, bind_v4, connect_v4, getsockname, listen, socket, AddressFamily, Ipv4Addr, Protocol,
17 let listen_sock = socket(AddressFamily::INET, SocketType::STREAM, Protocol::default()).unwrap(); in server()
77 socket(AddressFamily::INET, SocketType::STREAM, Protocol::default()).unwrap(); in client()
|
| /third_party/ffmpeg/doc/ |
| D | errno.txt | 103 ENOPROTOOPT POSIX +++..+ Protocol not available
123 EPFNOSUPPORT +++..+ Protocol family not supported
129 EPROTO POSIX ++4... Protocol error
130 EPROTONOSUPPORT POSIX - +++ss+ Protocol not supported
131 EPROTOTYPE POSIX +++..+ Protocol wrong type for socket
154 EUNATCH +..... Protocol driver not attached
|
| /third_party/protobuf/python/ |
| D | README.md | 1 Protocol Buffers - Google's data interchange format
8 This directory contains the Python Protocol Buffers runtime library.
16 Protocol Compiler (protoc). If you downloaded this package from PyPI
19 Protocol Compiler from some other source before you can use this
120 The complete documentation for Protocol Buffers is available via the
|