Fork of protobuf package about kyber HOT 4 CLOSED

Hi Alec, thanks for the note. FYI, my E-mail address is '[email protected]'.

Glad you found my protobuf code useful, and your improvements seem useful and well-done; thanks. I'm perfectly fine with this protobuf code being split out into a separate repository. Since it started out as a dedis group product, would you be open to moving the split-out version back under the DeDiS group umbrella, e.g., to 'github.com/DeDiS/protobuf', and I'll give you commit access so we can work together to maintain it going forward? (I'll also change our crypto library to use the split-out protobuf code when it needs to.)

And out of curiosity, what are you mainly using the protobuf code for?

Cheers
Bryan

from kyber.

Hi Bryan,

Moving the repository back under DeDiS/protobuf sounds like a good idea. Let me know once the repository is created and I can push, or you can clone+push. Whatever works.

We are using protobufs over HTTP to an iOS client written in Swift. We use alexeyxo/protobuf-swift on the client. We were originally using JSON, and the Go structures were the canonical public interface, but it was significant effort maintaining the deserialisation/serialisation code in Swift.

I chose your protobuf package (over using goprotobuf or gogoprotobuf) for two reasons:

1. The Go structures can still be the canonical source.
2. Interacting with go(go)protobuf generated structs is really irritating.

Thrift was a non-starter because there aren't any Swift generators for it yet.

Anyway, let me know once the repo is created and if you need me to do anything further.

Thanks,
Alec

from kyber.

OK, I set up a dedis/protobuf repo, and initialized it to include both the git history of the protobuf subdir of the original crypto repo (which was only a few commits) plus your repo's history. And you should have write access to the new repo. Hopefully we should be good to go; let me know if you encounter any problems.

Cheers
Bryan

from kyber.

Thanks Bryan, looks good!

from kyber.