Status: New
Owner:
Labels: Type-Defect Priority-Medium
New issue 394 by lichenw...@gmail.com: Improvement suggestion
http://code.google.com/p/protobuf/issues/detail?id=394
Hello, what is the proper way to share improvement suggestion? I did not
find any contact information.
My email is
Comment #1 on issue 394 by marc.gravell: Improvement suggestion
http://code.google.com/p/protobuf/issues/detail?id=394
You should *probably* discuss this in the group first:
https://groups.google.com/forum/?fromgroups#!topic/protobuf/V0gnLIWS744 ,
ideally checking the history first - it may
Thanks a lot for the explanation Marc.
I'm currently investigating some interop issues we're having and I'm
starting to realize that this might be the source of the problem.
[CollectionDataContract(Name = "ItemList")]
public class ItemList : List> where TItem : class
...
where
[DataContra
Well, until I get around to re-implementing it for v2, GetProto will
just make a quiet apology. But to answer your question, consider an example
such as ItemList
Item could be (I can't remember how v1 implements this) something
like
message Item_Customer {
optional Customer Item = 1;
Yes it does. Thanks.
Where can I read more about this disabling of list-handling and its effects?
On Thu, Jun 28, 2012 at 8:31 AM, Marc Gravell wrote:
> Well, until I get around to re-implementing it for v2, GetProto will
> just make a quiet apology. But to answer your question, consider an exa
Firstly, I must say that I don't generally recommend inheriting from lists
in this context. The code, as an implementation detail, tries to detect
things that look like lists, and switches to treat it as "repeated" data.
Sometimes, pretty rarely, something *looks* like a list, but should be
treated
I am kind of new to Protocol Buffers and really like it at beginning. Later
(now) I found out it has powerful framework for generate data structure
class from definition file but very limited entrance, only its own binary
format. It looks it have huge mansion but only one small window. It look
