The title says it!
I know that Jon Skeet was working on an implementation and I heard an interview (Dot net Rocks?) where he implied it was w.i.p.
The latest page just shows a version number. So, is it now production ready?
thanks
Share
Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
The title says it!
I know that Jon Skeet was working on an implementation and I heard an interview (Dot net Rocks?) where he implied it was w.i.p.
The latest page just shows a version number. So, is it now production ready?
thanks
There are two main implementations of Protocol Buffers:
I know Marc was in the middle of a major refactoring a little while ago; I don’t know if he still is.
My own port works as far as I’m aware (bar a bug in packed type sizing which was reported a couple of days ago) but lacks some polish around the generation side of things. Some users are interested in Silverlight compatibility which I’ve been working towards but haven’t tried yet. (Basically there are a few methods missing in Silverlight which I was using; I think I may have migrated all of them now – I need to check.)
I don’t know whether either implementation is in production use for any systems, but I’ll be happy to try to fix any bugs you raise. Note that I’m not intending to implement the “lite” PBs which appeared in the main 2.2 code; they would make the already-complicated inheritance nastier. I will be introducing an extra option to allow the mode (speed/size optimization) to be specified separately for C# soon.