Issue 4 in gwt-rpc-plus: Protobuf support

[gwt-rp...@googlecode.com]

Status: Accepted
Owner: mmastrac
Labels: Type-Defect Priority-Medium

New issue 4 by mmastrac: Protobuf support
http://code.google.com/p/gwt-rpc-plus/issues/detail?id=4

Protobuf should be reasonably simple to support in the same framework. We
could ship both compilers in the same tree, giving people the choice of
which
to use.

Needs some thought:

* Do we support the protobuf builder syntax on the client?
* If so, do we extend that to the Thrift objects?

--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings

[gwt-rp...@googlecode.com]

Comment #1 on issue 4 by t.broyer: Protobuf support
http://code.google.com/p/gwt-rpc-plus/issues/detail?id=4

My very own opinion: I'd rather have the exact same API on the client and
server side
(which means keeping the protobuf builder syntax on the client), so you
don't have to
"re learn" how to work with your objects depending on context (client- or
server-
side).

As for the serialization, it'd be good to support the same kind of JSON
serialization
as Closure Library: object with field name as key (ObjectSerializer with
KeyOption.NAME), object with field tag as key (ObjectSerializer with
KeyOption.TAG),
and array with field tag as index (PbLiteSerializer). Maybe the same
serializations
could be used for Thrift objects.