Hi, Thanks for the responses.
I have a few use cases in mind: 1) Provides an efficient binary representation for REST resources that can be used by multiple programming languages and platforms. 2) Allows REST to be primary way to support internal service invocations within en enterprise (replacing RMI, CORBA) 3) A HTTP friendly for the cloud with good performance. I'll go step by step: 1) Build a JAX-RS provider that can handle generated POJOs (maybe dynamic message too) from GPB so that we can exchange entities using "application/x-protobuf" media type. 2) Try to figure out how we can enable code gen for GPB with maven 3) Extend the provider so that GPB messages cab be serialized into JSON and XML. I just got the 1st working prototype. I'll contribute it via JIRA to jump start the effort. Thanks, Raymond ________________________________________________________________ Raymond Feng [email protected] Apache Tuscany PMC member and committer: tuscany.apache.org Co-author of Tuscany SCA In Action book: www.tuscanyinaction.com Personal Web Site: www.enjoyjava.com ________________________________________________________________ On Feb 16, 2011, at 9:54 AM, Luciano Resende wrote: > On Tue, Feb 15, 2011 at 4:46 PM, Raymond Feng <[email protected]> wrote: >> Hi, >> >> I'm interested in contributing a message provider for Google Protocol Buffer >> so that we can use Wink REST to exchange data in Google Protocol Buffer >> encoding. We can then add Apache Thrift support too. >> >> Any opinions? >> >> Thanks, >> Raymond > > Sounds interesting, what do you have in mind as for the model artifact > requirements, does it need to be a generated GPB, or you were planning > to add support for any pojo, and use the internal GPB APIs for > dynamically generate a PB message ? I'm asking because when I was > playing with dynamic messages, I was having issues to consume these > messages directly in a native GPB. If you want, I can commit GPB > Helper for Dynamic Messages to sandbox and we could collaborate on > this. > > Anyway, I believe this is going to be a good addition, particularly > when using JAX-RS rest services for inter-server communication where > parsing JSON/XML might not be as efficient. > > > -- > Luciano Resende > http://people.apache.org/~lresende > http://twitter.com/lresende1975 > http://lresende.blogspot.com/
