Lines Matching +full:multi +full:- +full:protocol
5 -------
7 This directory contains the RADIX test framework, which is a six-dimension
8 script-driven facility intended to facilitate execution of
10 - multi-stream
11 - multi-client
12 - multi-server
13 - multi-thread
14 - multi-process (in future)
15 - multi-node (in future)
17 test vignettes for network protocol testing applications. While it is currently
25 - single client ↔ single server
26 - multiple clients ↔ single server
27 - single client ↔ multiple servers
28 - multiple clients ↔ multiple servers
30 “Multi-process” and “multi-node” means there has been some consideration
31 given to support of multi-process and multi-node testing in the future, though
35 --------------------------------------
40 - Due to usage of the new QUIC server API, opcodes are no longer duplicated
45 - The framework is not limited to two objects (client and server),
49 - Scripts are now generated dynamically at launch time by functions rather
55 - As a result of the fact that scripts are now generated dynamically, the
56 in-memory representation of script operations has been improved as the ability
58 new representation is simpler, more compact, and more flexible. A stack-based
63 - Scripts are now named, rather than numbered, giving more useful debug output,
66 - Debug logging has in general been significantly improved and has been designed
69 - Logging of child threads is now buffered and printed after a test is complete,
70 which avoids non-deterministic interleaving of test output.
72 - The number of core opcodes for the interpreter has been dramatically reduced
77 - In the future, multi-process or multi-node testing will be supported.
78 The expectation is that multi-node testing will be facilitated by having the
85 - The core test interpreter is designed to be agnostic to QUIC and could be
88 protocol-specific bindings and support code, test operation definitions, and
91 - It is no longer needed to explicitly set the ALPN using an opcode when
96 - An explicit `OP_END` is no longer needed.
99 ------------
103 - **TERP** ([terp.c](./terp.c)), a protocol-agnostic stack-based script
106 - the **QUIC bindings** ([quic_bindings.c](./quic_bindings.c)), which defines
107 QUIC-specific test framework;
109 - the **QUIC operations** ([quic_ops.c](./quic_ops.c)), which define specific
113 - the QUIC unit tests ([quic_tests.c](./quic_tests.c)), which use the above