Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
Protocol Buffers
Home
+ new post
About this group
Join this group
Message from discussion What's the point of Protocol Buffers?
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
gsxr  
View profile  
 More options Jul 25 2010, 5:35 pm
From: gsxr <scott.suz...@gmail.com>
Date: Sun, 25 Jul 2010 14:35:57 -0700 (PDT)
Local: Sun, Jul 25 2010 5:35 pm
Subject: Re: What's the point of Protocol Buffers?
Print | View thread | Show original | Report this message | Find messages by this author

On Jul 21, 10:57 pm, Tim Acheson <tim.ache...@gmail.com> wrote:

> I generally create web services using WCF or ASP.NET MVC. I don't get
> the point of "Protocol Buffers". Am I missing something?

<snip>

> I don't need to write any code to do the serialisation, either. I just
> define the return type of the web method in my WCF project, or define
> an ASP.NET MVC Action that returns the object. The framework does the
> rest.

> Also, I rarely come accross a web service that returns anything other
> than strings, 32-bit integers and booleans. If I did, I'd probably
> question the architecture.

> Perhaps somebody could explain why I would want or need to use
> Protocol Buffers?

Your question is constrained, i.e. to WCF and .NET. The simple answer
is "you dont need to".

If your entire world is truly constrained in this way then I might
question your
architecture.

OK, that's being flip. What I really mean is that your question might
make PB look unsuccessful when it patently isnt. There is no
technology
in the .NET framework that delivers the same service across the
languages
and platforms that PB does.

If you can pull off all your development within the WCF+.NET island
then
not using PB is (perhaps) an optimal decision.

S.


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google