Repository navigation
codec-protobuf: a protobuf JsonCodec sibling for byte[] systems (e.g. Kafka) #37
Description
JsonCodec now speaks byte[] (#35), so a binary codec fits next to the JSON ones as a codec-protobuf module.
To decide
- Schema: a
.protofor the model.Content.Fieldsis an arbitrary JSON object (Map<String, Object>), so it needsgoogle.protobuf.Struct/Valueand a mapping both ways;Answer/Questionmap tooneof. - SPI:
JsonCodecis named for JSON, andclient-httpmust keep requiring JSON (the API speaks JSON). Either a protobuf codec stands alone (aProtobufCodecclass used directly, e.g. by a Kafka serializer), or the SPI splits into a genericCodecwithJsonCodecas the subtypeclient-httpasks for. Only worth splitting if something needs to be codec-agnostic. - Who consumes it: a concrete producer/consumer should drive the schema before we freeze it.
🤖 Generated with Claude Code
Activity
core: JsonCodec is now Codec
dfa1 commentedon Oct 4, 2026
Update: the SPI is now
Codec(byte[] in/out) as of #35, so a protobuf codec implements it directly. Remaining open point:client-httpmust still pick a JSON codec, since the API speaks JSON. If a non-JSON codec can be on the classpath,Codecneeds a way to say its format (e.g. a media type) soServiceLoaderdiscovery inclient-httpcan filter.Split modules into model (core), codec, contract (client) and impleme…