79d4107beb
Provide a means of declaring zero or more HTTP services, each with zero or more static HTTP resources. Static HTTP resources are those which have fixed paths[1] which are known prior to system initialization. Some examples of static http resources would be * a forwarder from '/' to '/index.html' * a REST endpoint with fixed path '/api/foo' and detail pointing at some implementation-specific function * a Javascript file in string form with fixed path '/js/util.js' * a 'construction' image with path '/res/work.png' * a gzip-compressed 'Hello' HTML file at '/hello.html' Without describing in any detail how static HTTP resources are organized or served by any given HTTP server, we can describe what static resources exist on a system in a common way that does not require any optional facilities (e.g. filesystem) and relies only on addressable memory. Additionally, for the purposes of simply allowing others to implement custom HTTP servers in a consistent way, or benchmarking implementations, or having a consistent testsuite to use across multiple implementations, it is helpful to have a common method to declare HTTP services and static resources for Zephyr. [1] https://en.wikipedia.org/wiki/URL Signed-off-by: Chris Friedt <cfriedt@meta.com> |
||
|---|---|---|
| .. | ||
| CMakeLists.txt | ||
| http_client.c | ||
| http_parser.c | ||
| http_parser_url.c | ||
| Kconfig | ||
| README_http_parser | ||