multiformats / multiformats/multicodec
Multicodec Idea: HTTP Response as one codec? HTTP Request as a second?
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 383
- Forks
- 221
- Avg merge
- 24d 6h
- Merged PRs (30d)
- 1
Description
@aarongoldman mentioned a crazy idea that I think might be useful for some web-interop usecases I've been looking into: a codec for CIDv1 that described HTTP requests and another for HTTP responses. This would certainly have made Webrecorder and Internet Archive easier to build! Could also be useful for all kinds of automated testing, CI, etc etc. Any obvious reason why this could be a disaster or a footgun?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no file, test, or implementation entry point. Start by reviewing the existing multicodec table conventions and the requirements for representing HTTP requests and responses; done would be a clear, maintainer-approved scope or decision on whether these codecs belong in the table.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100