Comments on: Using JAX-RS with Protocol Buffers for high-performance REST APIs http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/ Rants about Java and other internet technologies by Sam Pullara Mon, 08 Mar 2010 00:20:15 +0000 http://wordpress.org/?v=2.9.2 hourly 1 By: spullara http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-1017 spullara Fri, 16 Jan 2009 06:18:10 +0000 http://www.javarants.com/?p=955#comment-1017 Ah great, I'll add that in. Thanks! Ah great, I'll add that in. Thanks!

]]> By: Alek Storm http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-1016 Alek Storm Fri, 16 Jan 2009 06:04:18 +0000 http://www.javarants.com/?p=955#comment-1016 Protocol buffers actually does provide a way to sum the size of an object: message.getSerializesSize(). Everything is documented in <a href="http://code.google.com/apis/protocolbuffers/docs/reference/java/index.html" rel="nofollow">http://code.google.com/apis/protocolbuffers/doc...</a>. Protocol buffers actually does provide a way to sum the size of an object: message.getSerializesSize(). Everything is documented in http://code.google.com/apis/protocolbuffers/doc....

]]> By: spullara http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-840 spullara Thu, 15 Jan 2009 22:18:10 +0000 http://www.javarants.com/?p=955#comment-840 Ah great, I'll add that in. Thanks! Ah great, I'll add that in. Thanks!

]]> By: Alek Storm http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-839 Alek Storm Thu, 15 Jan 2009 22:04:18 +0000 http://www.javarants.com/?p=955#comment-839 Protocol buffers actually does provide a way to sum the size of an object: message.getSerializesSize(). Everything is documented in <a href="http://code.google.com/apis/protocolbuffers/docs/reference/java/index.html" rel="nofollow">http://code.google.com/apis/protocolbuffers/doc...</a>. Protocol buffers actually does provide a way to sum the size of an object: message.getSerializesSize(). Everything is documented in http://code.google.com/apis/protocolbuffers/doc....

]]> By: Subbu Allamaraju http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-818 Subbu Allamaraju Sun, 04 Jan 2009 02:28:58 +0000 http://www.javarants.com/?p=955#comment-818 Readability is not a problem as long as the media type is specific for each resource. Readability is not a problem as long as the media type is specific for each resource.

]]> By: sam http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-814 sam Thu, 01 Jan 2009 21:32:38 +0000 http://www.javarants.com/?p=955#comment-814 Actually I think his point is that it is even less useful since the protocol isn't self describing like XML or JSON. There is no way to read it at all without knowing the format of the protocol buffer. As an optimization or in isolation though, I think that is ok. Actually I think his point is that it is even less useful since the protocol isn’t self describing like XML or JSON. There is no way to read it at all without knowing the format of the protocol buffer. As an optimization or in isolation though, I think that is ok.

]]> By: Stefan Tilkov http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-813 Stefan Tilkov Wed, 31 Dec 2008 14:27:13 +0000 http://www.javarants.com/?p=955#comment-813 Sam, my guess is Subbu's point was that application/x-prototbug is about as meaningful as application/xml, i.e. it doesn't tell you anything about the actual content type, only about the syntax used to encode it. Sam, my guess is Subbu’s point was that application/x-prototbug is about as meaningful as application/xml, i.e. it doesn’t tell you anything about the actual content type, only about the syntax used to encode it.

]]> By: JAX-RS + Protobufs at subbu.org http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-812 JAX-RS + Protobufs at subbu.org Wed, 31 Dec 2008 06:59:48 +0000 http://www.javarants.com/?p=955#comment-812 [...] Sam Pullara writes in his post on Using JAX-RS with Protocol Buffers for high-performance REST APIs: [...] [...] Sam Pullara writes in his post on Using JAX-RS with Protocol Buffers for high-performance REST APIs: [...]

]]> By: sam http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-811 sam Wed, 31 Dec 2008 06:52:08 +0000 http://www.javarants.com/?p=955#comment-811 If you also wanted a client that only understood JSON or XML to access your web service you could also write a provider that could translate to and from JSON to Protocol Buffer objects. Then in each method you would add those as supported media types and it would map it for you based on the Accept header. Sam If you also wanted a client that only understood JSON or XML to access your web service you could also write a provider that could translate to and from JSON to Protocol Buffer objects. Then in each method you would add those as supported media types and it would map it for you based on the Accept header.

Sam

]]> By: Subbu Allamaraju http://www.javarants.com/2008/12/27/using-jax-rs-with-protocol-buffers-for-high-performance-rest-apis/comment-page-1/#comment-810 Subbu Allamaraju Wed, 31 Dec 2008 06:22:41 +0000 http://www.javarants.com/?p=955#comment-810 Just curious - what is the motivation for using protobuf over HTTP? One key issue with this approach is interop. B looking at the media type used in these examples "application/x-protobuf", HTTP clients would not know how to parse a representation. Comments? Just curious – what is the motivation for using protobuf over HTTP?

One key issue with this approach is interop. B looking at the media type used in these examples “application/x-protobuf”, HTTP clients would not know how to parse a representation.

Comments?

]]>