On Jul 21, 3:57 am, Tim Acheson <[email protected]> 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?
It'd be a similar set of reasons as to why we abandoned XML and JSON in favor of AMF when marshaling i/o interactions between our Flex RIA clients and our Java middle-tier. We don't use plain vanilla simpleton web service calls that just return a string or a number. Our RIA MVC clients request objects from the middle-tier and/or object graphs get pushed to them via BlazeDS Comet. We needed efficient object graph marshaling that is compact and performant even when returning very large result sets. Protocol Buffers addresses that same kind of scenario but with marshaling standard that is more universal than Adobe's AMF for the Flex/Flash Player. Indeed, as we're doing some C# .NET middle-tier interacting with Adobe Flex RIA client tier, we'll use Protocol Buffers for .NET and Flex bi- directional object graph marshaling. Likewise for our middle-tier interacting with our object database. We'll transition this over to using Protocol Buffers to marshal the object graphs (.NET interacting bi-directionally with C++). -- You received this message because you are subscribed to the Google Groups "Protocol Buffers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/protobuf?hl=en.
