We have a geographically distributed team and instant communications
are not possible. Given this constraint in mind, i am wondering how to
manage extensions. To clarify my question, consider a message like
message Request {
extensions 1 to 100;
}
Different developers would be working on extending
I disagree. You could encode field name in the binary. Then at de-
serialization, you can read the field descriptor and reconstruct the
field. There is absolutely no need for tags. They are indeed
cumbersome.
On Oct 22, 6:02 pm, Henner Zeller
wrote:
> On Fri, Oct 22, 2010 at 15:01, Paul wrote:
>
Is any one aware of a Sample code that would allow messages to be
dispatched in a generic fashion on the client side and receive and
locate the correct Message Handler on the server side in Java, given
client and server are remote.
I have a naive approach as follow
message AParticularRequest {
/
Since the client and server are remote, i am not sure how i can send
Descriptor along with message?
On Oct 27, 1:14 pm, Adam Vartanian wrote:
> > I need a generic parser in java, which can de-serialize PB bytes
> > buffer into a Message or GeneratedMessage. But, GeneratedMessage
> > provides no
In typical WS-* webservice, WSDL describes a service interface,
abstracts from underlying communication protocol and serialization and
deserialization as well as service implementation platform.
Where does PB fits in this picture? Is .proto file, equivalent to
WSDL? Or should i view it as simply
