Serialization
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 11
- Forks
- 3
- PR merge metrics
- No merged PRs in 30d
Description
In PR #8, @dob commented on the serialization code. We will eventually switch to a custom serialization format as defined by the PPSPP RFC, but for now we're using JSON. This issue tracks the software architecture for handling this in a way that will make it easy to swap back and forth as needed.
I think go-multicodec will allow a peer to support both codecs at once -- decoding based on an incoming header. So we could implement a new codec based on the RFC spec and then add it to the multicodec that the peer supports. I'm not sure, need to think more about this.
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
Review the serialization discussion in PR #8 and the current JSON-based approach. Read the PPSPP RFC and investigate whether go-multicodec can support both codecs by decoding an incoming header. Done means an agreed architecture and scoped plan for switching between serialization formats.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100