You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Maintaining the protobufs in a separate repo would make it easier to ensure that both CONIKS implementations use compatible protobuf messages. Any changes to the protobufs could then be easily propagated to both implementations. This repo would contain the compiled protobufs for each supported language, which can then be imported by each implementation.
The text was updated successfully, but these errors were encountered:
Yeah, I think so, too. I also think that we can adopt protobufs into our storage backend hook. It would replace the Deserialize and Serialize problem we're facing.
Maintaining the protobufs in a separate repo would make it easier to ensure that both CONIKS implementations use compatible protobuf messages. Any changes to the protobufs could then be easily propagated to both implementations. This repo would contain the compiled protobufs for each supported language, which can then be imported by each implementation.
The text was updated successfully, but these errors were encountered: