(duplicate with existing answers
here:
https://stackoverflow.com/questions/45501605/is-it-possible-to-use-google-protobuffer-to-serialize-data-without-prefixing-the)
--
You received this message because you are subscribed to the Google Groups
"Protocol Buffers" group.
To unsubscribe from this
Formally: no.
Practically: almost always
You shouldn't **demand** it.
Basically, it goes like this:
- the spec asks that writers *should* write fields in order
- the spec asks that readers *must* allow fields in any order
- data can be concatenated as a merge, meaning fields can appear out of
the language guide is very clear and explicit that this is intentional; it
is nothing to do with the C# part, and will behave the same for any
language:
> You can add fields of any type, but cannot use the required, optional, or
repeated keywords.
can you perhaps clarify the question?
On 2 Jul 2017 2:18 p.m., "Jing Lupeng" wrote:
>
> https://developers.google.com/protocol-buffers/docs/encoding#structure
>
>
>
>
Basically, if I have
message Foo {
int32 x = 1;
int32 y = 2;
}
message Bar {
map items = 1;
}
And I serialize 2 fragments appended:
items = { 1: { x: 123 } }
and (as the second appended chunk)
items = { 1: { y: 456 } }
And now I deserialize the entire chunk; is the
javascript (including browsers and node.js) can handle binary data just
fine, and my understanding is that this functionality is exposed by the
javascript implementation. I can't opine on that hugely, because my use of
protobuf is primarily backend - server-to-server, or server<--->storage.
wow, auto-complete went mad with that, sorry. "nay" => may; "red is" =>
redis, etc.
On 21 Jun 2017 8:22 a.m., "Marc Gravell" <marc.grav...@gmail.com> wrote:
> "You wish to express data in a mechanism that can be expressed as a byte
> str
"You wish to express data in a mechanism that can be expressed as a byte
stream, and/or communicate that between systems that nay or may not be
using different architectures, in a way that is efficient both
computationally and in terms of bandwidth; and a platform independent tool
to express the
(I'm assumig the "optional" isn't there in the real example)
You can't simply change between proto2 and proto3. In proto3 everything is
optional with an implicit zero default. This is fundamentally incompatible
with consumers who have a "required" expectation **unless** you happen to
never send
In descriptor.proto, it asks public authors to request extension numbers (for
the DSL) via protobuf-global-extension-regis...@google.com
I've done this, but without response. Is this address being monitored?
--
You received this message because you are subscribed to the Google Groups
It is supported in the proto2 *language*, but you'll need to use a *proto
compiler version* that understands it. Depending on the implementation
(i.e. which language and library you are generating for), you *may* also
need to use a *library* version that has additional features to support
maps.
Oops; I meant to reply to group; email is hard...
(repeats response)
What protoc compiler version are you using? what does protoc --version say?
It should be 3.3.0 or similar.
The following works fine using protoc (note it defaults to protogen -
you'll need to change the drop-down to protoc
This will mostly be useful to library maintainers, etc. I know that protoc
has some tools in this area, but I found them ... "unhelpful" for my
purposes.
I very often end up digging through protobuf files of unknown origin
without a schema etc, to either help support a stuck user, or to
That's not something that protobuf targets. If you have a syntax that
allows you to convey an expression as a string or similar, then by all
means do that - but protobuf will just see it as an opaque string. Note
that there are usually a range of concerns when transferring executable
code (of any
I can't speak for the design choices - but *as I understand it*, the key
point of protobuf is to enable things to work well cross-platform. That
means that at the DTO level, things need to be *possible* to implement in a
wide range of languages, and the reality is that not all frameworks would
Hey all; I've been doing some work with protobuf-net lately to bring it up
to date with proto3, "timestamp", and all those things. As part of that,
I've been reworking my entire code-gen pipeline, with the result that I
accidentally wrote an interactive online editor while I was avoiding
es/download/v3.0.0/protoc-3.0.0-win32.zip>
> for
> compiler? Can you also give me ur input (.proto file) for that you gout
> output *https://gist.github.com/mgravell/4967b490d40f13300919b018af23b282
> .
>
> Thanks for your time.
>
>
> On Fri, Sep 9, 2016 at 7:08
You'd be best off creating it by hand, but if you want a starting point,
you can use protobuf-net to get some hints; add
[ProtoContract(ImplicitFields = ImplicitFields.AllPublic)] to your root
type (UAVState?), and use something
like Console.WriteLine(Serializer.GetProto()); to see the
content. I
I can't reproduce this outputting a 0x0; my example is below, and
outputs 22-0A-12-08-73-6F-6D-65-43-69-74-79 - the null nested message is
simply completely omitted; the contents are:
- 2 bytes field-header and length-prefix for the location member
- 2 bytes field-header and length-prefix for the
Just for visibility; we've discussed this more on github, and it *looks* to
be a protostuff decoding issue, not a protobuf-net encoding issue; Johannes
will take our findings to protostuff for further investigation.
Arbitrary link is
arbitrary:
You cannot. What you describe is not what protobuf offers.
On 7 Oct 2014 00:55, RPMASA rudram...@gmail.com wrote:
Hi,
I have structured binary file specifying size of each element in bytes.
How can I mentioned them in ptoto file?
No. Description Data Value Variable Type Number of
My first thought is: what makes you think that you have read an entire
frame of data, and a *single* frame of data? socket read very rarely
conveniently forms itself into complete frames. Please see http://tiny.cc/io.
My second thought is: you told it to use the *entire* buffer, not just the
valo
Also; don't swallow exceptions. In fact, if you can't do anything useful,
don't even try/catch - just let it explode.
Marc
On 12 September 2014 10:44, Antonio Ramos ninira...@gmail.com wrote:
Hi all, this is my first time with protobuf protocol and protobuf-net.
I have the following
:
But for use this constructor i have to know the message size, is´nt it?
how can i do it? with a sizeof of the proto class??
2014-09-12 21:22 GMT+02:00 Marc Gravell marc.grav...@gmail.com:
My first thought is: what makes you think that you have read an entire
frame of data, and a *single* frame
This is specific to protobuf-net. The library does not currently expose any
custom serialization extension point; to do that in a way that is genuinely
useful, while not allowing the caller to break the wire format, is quite
tricky. To date: it hasn't been necessary. If you can clarify *why* you
This is specifically protobuf-net; firstly, you should be able to add
-p:lightFramework to the command - that omits a few things that don't work
on all frameworks, including [Serializable] iirc.
However, you can also just edit CSharp.xslt to make any necessary changes.
Stick it alongside
forward to hear from you.
Regards
Desmond
On Thu, Jul 10, 2014 at 9:18 PM, Marc Gravell marc.grav...@gmail.com
wrote:
Ooh, the idea of allowing SQL over a service boundary sends all kinds of
shivers up my back, and not the good kind of shivers. On your head be it,
but: I wouldn't do
sqlcommands. which means we
need to serialize DataTables as part of an object. I there a way we can
achieve this with protobuf.
Do you have any workaround/alternative or suggestion?
Regards
Desmond Davids
On Friday, 16 July 2010 08:00:25 UTC+2, Marc Gravell wrote:
From the message
The simple answer would be use the existing oversized types, and cast at
the caller. Varint data in particular will either be 1 byte or 2 (50%
each) for byte values. For longer sequences (rgba etc) there are existing
fixed-32 and bytes.
If the intent is to add a wire type to precisely represent a
The protobuf specification doesn't have the notion of object identity.
protobuf-net *does* (as an optionally enabled feature), but it doesn't
currently work for list items directly, although I suspect it probably
should. Since it would break the format, though, it would need explicit
enabling if I
Oops; meant to press reply-all, not reply, but:
This relates to protobuf-net. The only time the Name property is used is if
you reverse-generate from code to .proto via Serializer.GetProto (or the
similar method on RuntimeTypeModel).
On 23 May 2014 13:23, Sam Eaton nuluv...@gmail.com wrote:
Oops, meant to reply-all!
On 16 May 2014 19:34, Marc Gravell marc.grav...@gmail.com wrote:
This is specifically protobuf-net; I have received a repro case from Marco
separately via email, so I will investigate and post back here and
directly, but short version don't know off the top of my head
protobuf is a binary-safe protocol, and is not impacted by contents such as
\r, \n or \t. In particular, text content is utf-8 encoded and
length-prefixed - it simply *does not care* what is inside the text. I
suspect any problem you are having relates to how you are transporting and
processing
Protocol buffers in the public project consists primarily of the
serialization framework; serialization is always necessary when
communicating, and frameworks/formats are aplenty, including xml, json,
etc. The primary features of protocol buffers (protobuf) are:
- efficient binary on the wire
This looks to be protobuf-net specific. Note that protobuf-net includes
SerializeWithLengthPrefix and DeserializeWithLengthPrefix which can be used
to simplify working with multiple separate logical messages on a single
stream (such as against a socket), without ever over-reading.
Also - it
This is specific to protobuf-net; the inclusion of System.Xml is basically
linked to the PLAT_XMLSERIALIZER build symbol, which for the Full/Unity
configuration is currently:
DefineConstantsTRACE;FEAT_COMPILER PLAT_BINARYFORMATTER
PLAT_XMLSERIALIZER PLAT_NO_INTERLOCKED
Can you be very specific with what you mean by connect with .NET Database
using Protocol Buffer? What **exactly** are you trying to do? And since
you are mentioning Http Request, Http Response and PHP - does
Database here really mean web-server ? Ultimately, the mechanism for
getting protobuf data
If your intent is to get text from a to b, then there won't be a problem.
Protobuf uses utf-8, but that is an implementation detail that you should
never see. If your concern is that it may take more bytes in utf-8 than
utf-16 (for the codepoints in question), the you can always use a bytes
type
On 7 Nov 2013 20:32, Marc Gravell marc.grav...@gmail.com wrote:
What platform? But basically protobuf should be treated as a BLOB. Then
you have two choices:
- send it as a payload in an existing messaging stack
- write your own messaging layer on top of sockets - noting that because
to the latest mono 3 master because of a
threading bug that was fixed 2 weeks ago, now this:)
Chris
On Tuesday, October 15, 2013 10:45:46 AM UTC-7, Marc Gravell wrote:
Firstly: exactly what version is this? There was a bug in 663 relating to
threading (and which only exhibited after extended usage
Firstly: exactly what version is this? There was a bug in 663 relating to
threading (and which only exhibited after extended usage) that was fixed in
something like 668. If you are using something = 663 and 668 then please
update and retry.
Marc
(protobuf-net)
On 15 Oct 2013 16:22,
I don't do much... no: *any* C++/CLI - but I guess the conflict here is
that the c++ generated classes are not going to be CLI-friendly. So you
need to either use a c++ library and c++ classes, or a managed library and
managed classes.
If your framework is unmanaged c++, then I *suspect* your
On 7 October 2013 10:45, Barzo dba...@gmail.com wrote:
In a meanwhile I have built the .cs generated file into a separate DLL
assembly and I added it (linked) to my C++/CLI project.
Indeed, compiling it as C# and referencing/linking was what I meant - i.e.
using the C# *from* C++/CLI, rather
This is specifically protobuf-net. I'd be happy to take a look, but is
there any context you can add about your specific model? As far as I know
there isn't a *general* reason for it to fail here. At the simplest : are
you able to make your model DLL available to me to use as a repro?
Note: due
Build r668 went out earlier to both nuget and google-code. I guess the 666
build was doomed to have an evil bug hiding away in there somewhere.
Marc
On 29 September 2013 10:06, Marc Gravell marc.grav...@gmail.com wrote:
Yikes. Bug. Basically, the position field wasn't being reset when used
Yikes. Bug. Basically, the position field wasn't being reset when used
from the pool. This field is used for two main purposes:
- error reporting (telling the user at what offset it glitched)
- tracking sub-object ranges
I suspect that because it didn't reset, the field overflowed. This won't
That would depend entirely on what exact DLL you are using. Those methods
exist on all Full builds. I'm guessing you have referenced one of the
CoreOnly builds. The CoreOnly builds are intended for use with the
precompiler (
In all honestly I can't answer that off the top of my head, and I'm not at
a PC. I can investigate and get back to you.
Marc
On 19 Sep 2013 17:54, David Deutsch da...@reverenddave.com wrote:
I have the following member of a class:
public SerializableDictionaryint,
What is the property? A sub-object? A List? If the serializer doesn't think
it needs to call the setter: it won't. For example, the typical list
handling code could be paraphrased (not the actual implementation) as:
var list = obj.SomeList;
bool setValue = false;
if(list == null) {
Yes, OverwriteList should fix this. IgnoreListHandling does something very
different that doesn't apply here (see the intellisense comments for full
usage
Marc
On 19 Sep 2013 17:21, David Deutsch da...@reverenddave.com wrote:
So I *think* what is happening is that protobuf does a get of the
This is specifically a protobuf-net question. I am guessing that somewhere
in your model is a property / field declared simply as object. That isn't
enough information for ptotobuf-net to work with, because the protobuf data
format doesn't include type metadata. It would have no way of recreating
Protobuf supports recursive schemes - but note that each object is separate (it
is a tree, not a graph). For example, descriptor.proto includes the
self-referential DescriptorProto (which is a message in language terms)
// Describes a message type.
message DescriptorProto {
optional string
This is specifically a protobuf-net question.
In short, yes - that is fine... ish. If you add the numbers manually ***and
get them right***, then it will work. However, your example actually gets
them wrong: the protobuf-net library specifically assumes an *alphabetical*
order for the properties
,
this would be a good choice) but the above is much easier for ad-hoc
scenarios.
Marc
(protobuf-net)
On 15 July 2013 19:48, Marc Gravell marc.grav...@gmail.com wrote:
This is specifically a protobuf-net question.
In short, yes - that is fine... ish. If you add the numbers manually
***and get them
Hi - you also asked this on stackoverflow, and I asked you a few questions
- can you answer them? Ta
http://stackoverflow.com/questions/17173588/protobuf-wcf-no-model-instance-has-been-assigned
Marc
On 19 Jun 2013 21:59, Andrew McCormack mccor...@gmail.com wrote:
I am getting this error:
No
Protocol buffers is language and platform independent, so yes: you can
share data happily without worrying about what each is.
However, it is a serialisation layer *only*. It does not include RPC etc.
If you want to get data from a to b, it is fine. Anything to do with
relaying function calls you
Have you looked through the examples on the protobuf project site?
On 13 Jun 2013 18:09, Genius genius.b...@gmail.com wrote:
I want to use protocol buffer files.
I am trying to build schema and I have data of various types like int,
string, byte.
so to declare the byte data of 4 bytes how do
There is nothing UB the specification to enforce that. You would have to
use your own checks.
On 11 Jun 2013 01:55, oxlc li.c...@openx.com wrote:
Hi everyone,
Through some quick searching I couldn't find any discussion about
specifying a repeated field that must have at least one of them in a
This is a protobuf-net specific question. The answer to that depends on
what you want to do. And I should stress that using attribute decoration is
a lot simpler (and is what you get if you start from .proto). But basically:
RuntimeTypeModel.Default
.Add(type(Customer), false)
I don't know about project/product lists, but you could look to
https://code.google.com/p/protobuf/downloads/list - 50,000 downloads of
protoc 2.5 since late February, which suggests reasonable usage - and that
doesn't include packages that either don't use protoc, or which embed
protoc. You could
think it is more of a bug in the protoc implementation that it fail's
to parse such a message.
Kind regards,
Jonas
On Tuesday, May 14, 2013 6:50:00 PM UTC+2, Marc Gravell wrote:
I should clarify: when talking about groups I should emphasise that
Google have marked that feature plagued. Which
have any plan to change it.
As to your performance concern, only benchmarks can tell. So far I haven't
seen such data showing that prefixing a fixed-size length is a performance
gain.
Kind regards,
Jonas
On Tuesday, May 14, 2013 6:50:00 PM UTC+2, Marc Gravell wrote:
I should clarify
I asked about this a few years ago (feel free to search the archive - I
couldn't find it; I believe I used the term subnormal forms for this).
IIRC the answer then was along the lines of hmmm looking at the
current implementation that will probably work, but it isn't guaranteed and
won't be
interest to me, since I don't use the Google API).
Marc
On 14 May 2013 17:47, Marc Gravell marc.grav...@gmail.com wrote:
I asked about this a few years ago (feel free to search the archive - I
couldn't find it; I believe I used the term subnormal forms for this).
IIRC the answer then was along
headerMsgLenMsgheaderMsgLenMsg... is the standard form of
protobuf repeated data. A header value of 10 is the standard form for a
length-prefixed field with key 1. If you want to read all the objects
together, then write a wrapper message, i.e.
message animals {
repeated animal items = 1;
}
On 7 May 2013 19:40, Marc Gravell marc.grav...@gmail.com wrote:
I don't know about the other stuff. But: protobuf does not include any
form of encryption. Since it only handles serialization (not full RPC) it
does not include any authentication logic either. The data is serialized
without
On 7 May 2013 18:53, Marc Gravell marc.grav...@gmail.com wrote:
Protobuf has a fee encodings for integer data, which basically come down
to:
- varint (with or without zigzag)
- fixed-32 (always 4 bytes)
- fixed-64 (always 8 bytes)
For 16 bits, you will do best with varint. If the data can
The outermost message is not stored with a length; this allows multiple
messages to be merged by concatenation. The default behaviour for a protobuf
parser at the root-object is read until you run out of data. If you have
written multiple messages without some kind of framing (usually adding
, Unsupported Message Type: + _type);
}
Thank you all for helping out... :)
On Saturday, March 23, 2013 1:35:27 PM UTC-5, Marc Gravell wrote:
Protobuf-net does not swallow any errors - if bad things happen in
shouts loudly. Additionally the API is thread safe - during deserialization
Sorry - intended to cc the list for reference purposes
---
This is protobuf-net specific; sorry for delay bit I'm on a family weekend
and my wife deliberately picks destinations far far away from cell towers.
To explain: protobuf-net always starts from
this seems to be a resurrection of a protobuf-net specific discussion, so
let me jump in...
The SerializeWithLengthPrefix method, by default, aims to represent data in
a way that is a valid protobuf stream - in particular, as though it were
simply a member of a parent object or list. As such, it
Hi again. I already replied with a few comments / questions on stack overflow.
I'm happy to try to help, but at the moment you haven't given me much context
to work on.
Marc
(protobuf-net)
On 7 Dec 2012, at 11:28, Evangelist murali.po...@gmail.com wrote:
Hello folks,
I have a wcf service
This sounds very protobuf-net specific; it might be easier to take this
off-group, but I think I'll need a bit more context; in particular, since it is
a PCL type, what runtime is this on when erroring? Also, are you using
Serializer.*, or are you creating an instance of the custom serializer
AdjustValue;
/// remarks/
[System.Xml.Serialization.**XmlAttributeAttribute()]
public System.Single[] Values;
}
Regards
Shailendra
On Wednesday, 1 August 2012 11:51:01 UTC+5:30, Marc Gravell wrote:
And in this model, what is FloatData, StringData, IntData, etc
And in this model, what is FloatData, StringData, IntData, etc?
This is certainly solvable with protobuf-net, but to do a complete example
I'd need to see those additional types.
Marc
(protobuf-net)
On 31 July 2012 14:14, Shail shailendranalw...@gmail.com wrote:
public class Param
{
System.Single[] Values;
}
Regards
Shailendra
On Wednesday, 1 August 2012 11:51:01 UTC+5:30, Marc Gravell wrote:
And in this model, what is FloatData, StringData, IntData, etc?
This is certainly solvable with protobuf-net, but to do a complete
example I'd need to see those additional
protobuf-net indeed needs *some* way to associate protobuf numbers with
members; one of the ways it supports is `[XmlElement(Order=n)]`, but to
confirm: yes the n needs to be = 1, and yes, since `[XmlAttribute]`
doesn't specify any such number, protobuf-net can't use that in any
meaningful way.
to this stuff, so if I'm not making any sense at all let me
know and I'll return with a smarter question.)
Joel
On Wednesday, June 27, 2012 4:07:49 PM UTC-4, Marc Gravell wrote:
The data is of course compatible. A `ListFoo` is directly mappable to
.proto via for example:
message
June 2012 13:51, Joel Carrier j...@joelcarrier.com wrote:
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 marc.grav...@gmail.comwrote:
Well, until I get around to re-implementing it for v2
On Wednesday, June 20, 2012 9:05:49 AM UTC-4, Marc Gravell wrote:
(note: this is specific to protobuf-net, not protocol buffers more
widely), but yes: that (a generic list) would work fine, as long as the
property has been marked for serialization and given a number. There also
doesn't need to be a set
(note: this is specific to protobuf-net, not protocol buffers more
widely), but yes: that (a generic list) would work fine, as long as the
property has been marked for serialization and given a number. There also
doesn't need to be a set accessor, although it can make full use of a
set - i.e. if
I answered this at stackoverflow (http://stackoverflow.com/a/11083229/23354)
The main problem was the data-types in V3DDelta not matching the contract
(note: there are tools for generating classes from a .proto definition).
The particular code for reading the data stored via writeDelimitedTo
it only has to be unique to the particular message - not unique globally.
The why is simply: because that is what it uses on the wire to identify
different members.
If they weren't unique, clearly it wouldn't work. If they weren't explicit
(but were, say, assumed positionally) then it would not
was complaining
about shared ids. [?]
On Mon, Jun 4, 2012 at 11:44 AM, Marc Gravell marc.grav...@gmail.comwrote:
it only has to be unique to the particular message - not unique globally.
The why is simply: because that is what it uses on the wire to identify
different members.
If they weren't unique
This relates to protobuf-net; you've already emailed me directly, and I
replied. You raised an issue report: I replied. Please read (and act on) my
existing replies.
Marc
On 4 Jun 2012, at 12:00, Farooq Mushtaq farooqmushta...@gmail.com wrote:
While serializing I am getting error Possible
Well, protobuf-net certainly includes them (it just does a simple UTF-8
conversion, nothing more), and I'm pretty sure the C++ side will be
handling them fine.
My guess would be that they are being lost in your code with whatever file
/ network handling you have in place. In particular, any code
Sorry, I didn't see this at the time - do you have any kind of concrete,
reproducible example here?
Marc
On 28 February 2012 20:48, costa costa.ba...@gmail.com wrote:
Have you seen this?
The list is an IListTestClass where TestClass has the ProtoContract
attribute and all its members have
If you mean protobuf-remote (which I'm not personally familiar with),
that is an RPC stack. It will help you send and receive messages. Any
database requirements you must handle separately. There is a manual
page linked for both C# and C++ - http://code.google.com/p/protobuf-remote/
Marc
On Dec
a copy of the current
code compiled with FEAT_SAFE?
Marc Gravell
(protobuf-net)
On 19 December 2011 19:11, Scott Moore scott.moor...@gmail.com wrote:
I readily admit that I am a bit of a novice developer (I work in a
small business and we all help as much as possible). I came across
@Bob - based on the version numbers, Yury is talking about protobuf-net
(one of the 3rd party .NET implementations), using it on iOS via MonoTouch
or Unity
@Yury - sorry, I completely didn't see this thread; but indeed, the iOS
folder got accidentally dropped when I updated my build script, and
that could also just mean stable and not needing massive work - there
haven't been any significant changes to the protobuf format since packed
arrays (the most recent commit).
(I honestly don't know either way; I just don't think it is quite safe to
assume lack of activity means abandoned here)
Inside any standard implementation? None. And I doubt that is something that
would be added anytime soon (if ever). You could of corse create some private
branch combining elements of protobuf with your own more specific needs.
Marc
On 20 Oct 2011, at 12:32, Phillip Dann Ward
at 11:02 AM, Marc Gravell marc.grav...@gmail.com
wrote:
Well, firstly protobuf is not a text format, so UTF-8 is not the way to
start. What is it you need? Note that the protobuf format is ambiguous
unless you already know the schema (the same data can be interpreted in
different ways). However
Well, firstly protobuf is not a text format, so UTF-8 is not the way to start.
What is it you need? Note that the protobuf format is ambiguous unless you
already know the schema (the same data can be interpreted in different ways).
However, if you read the encoding spec, you should be able to
Addressed on stackoverflow:
http://stackoverflow.com/questions/7793527/protobuf-net-serializing-ienumerablet
Marc
On 17 Oct 2011, at 12:35, Broken Pipe brokenpipe.co...@gmail.com wrote:
I'm trying to use ProtoBuf-net in Silverlight project, I'm using my
existing domain objects, which define
In the next build, this has been tweaked:
type = source.DeserializeType(typeName);
if(type == null)
{
throw new ProtoException(Unable to
resolve type: + typeName);
}
So,
In standard use, protouf-net is fully contract based and doesn't care what
*types* are involved; this only matters if you are using the DynamicType option
(which is outside the core protobuf stuff). If the types aren't stable, there
is an event on the TypeModel that can be used to map in both
I answered this where you cross-posted on stackoverflow:
http://stackoverflow.com/questions/7717036/serialize-protocol-buffer-file-into-xml-text-format
To repeat; in most cases, the generated code **should already** work
perfectly well with XmlSerailizer (the inbuilt .NET xml serialization tool),
Protocol buffers itself only (AFAIK) describes the serialisation format; it
does not define RPC. If you add an http-based RPC stack, then it will be
http-based, but that is nothing to do with protocol buffers, you could (and
many do) use raw sockets just as well.
Marc
On 30 Sep 2011, at
Ooh, that sounds like me, then. It works fine against the current v2 code; I
do seem to recall there was a bug at some point in v2 that behaved like
this. If you are using v2, please make sure you have a recent version. If
you are using v1 and this happens /there/, then my flabber is officially
101 - 200 of 335 matches
Mail list logo