net: http: define http service and resource iterable sections #55430
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
In draft / blocked on #55429 |
cfriedt
force-pushed
the
add-http-service-and-resource-iterable-sections
branch
from
d92d8f1 to
a5f394f
Compare
|
Also, just to clarify, yes, this does allow multiple HTTP servers to operate simultaneously (or a single server, serving multiple ports). |
cfriedt
force-pushed
the
add-http-service-and-resource-iterable-sections
branch
from
a5f394f to
71b333e
Compare
|
|
I would say that possibly the most useful result of this change is that it allows us to test or benchmark any HTTP server implementation using the same testsuite |
|
This is important to get in well before GSoC contributors finish preparing their applications / sample code. |
cfriedt
force-pushed
the
add-http-service-and-resource-iterable-sections
branch
from
71b333e to
2455c07
Compare
cfriedt
force-pushed
the
add-http-service-and-resource-iterable-sections
branch
2 times, most recently
from
3be5979 to
e585a3f
Compare
cfriedt
force-pushed
the
add-http-service-and-resource-iterable-sections
branch
4 times, most recently
from
6ee42b1 to
9617232
Compare
rlubos
reviewed
Mar 6, 2023
cfriedt
force-pushed
the
add-http-service-and-resource-iterable-sections
branch
from
9617232 to
e66d15b
Compare
rlubos
previously approved these changes
Mar 6, 2023
cfriedt
force-pushed
the
add-http-service-and-resource-iterable-sections
branch
5 times, most recently
from
c76d40e to
d1fc992
Compare
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>
Add tests to verify the newly-added HTTP service and resource macros. Signed-off-by: Chris Friedt <cfriedt@meta.com>
cfriedt
force-pushed
the
add-http-service-and-resource-iterable-sections
branch
from
d1fc992 to
5df0df5
Compare
rlubos
approved these changes
Mar 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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] that are known prior to system initialization. Some examples of static http resources would be
Without loss of generality in 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
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