-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Labels
Milestone
Description
Suggestion / Feature Request
Consumers of our crate will very likely (and frequently) need to parse HTTP response data from a remote server. Other crates exist that perform this task. It may be that we decide to adopt one of these crates as our out-of-the-box HTTP parser and include it as a transitive dependency to our crate. If so we should provide the ability to opt for other HTTP parsers of our users' choosing.
Notes:
- This may include opening a new discussion asking for community feedback
Definition of Done:
- The following questions should be answered:
- What exists in terms of
no_std
HTTP parsers? - Is it feasible to include one in our crate?
- The pros and cons of including an HTTP parser in our crate vs considering it the responsibility of the user
- Is there a common trait which HTTP parsers can/do implement that we can use to allow users to choose their own crates?
- What exists in terms of
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
No status