blocks|key|734928|text|协议缓冲区项目肯定不是封闭源。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|734929|你对哪种语言/平台感兴趣？|734930|对于Java、C%2B%2B和Python，有一个谷歌代码。|unordered-list-item|offset|length|734931|对于C#，至少有三个项目(包括我的或马克氏)|734932|有关其他语言/平台，请参见相关维基页面|734933|请注意，尽管协议缓冲区中有存根RPC支持，但Google尚未发布其实际RPC层，因此您必须提供自己的RPC层。考虑到基本上您将传递请求消息并返回响应消息，那么在现有协议(例如HTTP+)上对其进行分层并不困难。|734934|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/apis/protocolbuffers/|1|http://github.com/jskeet/dotnet-protobufs/tree|2|http://code.google.com/p/protobuf-net/|3|http://code.google.com/p/protobuf/wiki/OtherLanguages^0|0|0|L|4|0|0|F|2|1|I|3|2|0|D|6|3|0|0^^$0|@$1|2|3|4|5|6|7|12|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|13|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|14|8|@]|9|@$G|15|H|16|1|17]]|A|$]]|$1|I|3|J|5|F|7|18|8|@]|9|@$G|19|H|1A|1|1B]|$G|1C|H|1D|1|1E]]|A|$]]|$1|K|3|L|5|F|7|1F|8|@]|9|@$G|1G|H|1H|1|1I]]|A|$]]|$1|M|3|N|5|6|7|1J|8|@]|9|@]|A|$]]|$1|O|3|-4|5|6|7|1K|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]|W|$5|R|S|T|A|$U|X]]|Y|$5|R|S|T|A|$U|Z]]|10|$5|R|S|T|A|$U|11]]]]

The Protocol Buffers project definitely isn't closed source.

Which language/platform are you interested in?

<ul>
<li>For Java, C++ and Python there's the <a href="http://code.google.com/apis/protocolbuffers/" rel="noreferrer">Google code</a>.</li>
<li>For C# there are at least three projects (including <a href="http://github.com/jskeet/dotnet-protobufs/tree" rel="noreferrer">mine</a> or <a href="http://code.google.com/p/protobuf-net/" rel="noreferrer">Marc's</a>)</li>
<li>For other languages/platforms, see the <a href="http://code.google.com/p/protobuf/wiki/OtherLanguages" rel="noreferrer">relevant wiki page</a></li>
</ul>

Note that although there's stub RPC support in Protocol Buffers, Google hasn't released its actual RPC layer, so you'd have to provide your own. Given that basically you'd pass a request message and return a response message, it's not that hard to layer it over existing protocols (e.g. HTTP POST).

blocks|key|734868|text|我不认为协议缓冲器是封闭的。这个页面意味着不同的内容，并且有源代码下载。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|734869|entityMap|0|LINK|mutability|MUTABLE|url|http://code.google.com/p/protobuf/^0|4|5|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

I don't think <a href="http://code.google.com/p/protobuf/" rel="nofollow noreferrer">Protocol Buffers</a> are closed-source. The page implies differently, and there are source downloads.

blocks|key|734600|text|很可能不是最好的人选，但为了完整起见，我想补充一下，有一个XML二进制编码。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|734601|entityMap|0|LINK|mutability|MUTABLE|url|http://www.w3.org/XML/Binary/^0|T|8|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Quite possibly not the best candidate, but for completeness' sake I'd like to add that there's a <a href="http://www.w3.org/XML/Binary/" rel="nofollow noreferrer">binary encoding for XML</a>.

blocks|key|401942|text|我建议你重新考虑谷歌协议缓冲区。所有主要平台都有许多开源实现，包括由Google自己发布的C%2B%2B/Java/Python。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|401943|正如Jon上面提到的，PB规范没有定义RPC模型，但是使用PB定义您自己的RPC非常容易。|401944|或者，您可以查看ASN.1。有很多应用程序使用ASN.1。|401945|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

I would suggest that you reconsider Google Protocol Buffers. There are many open source implementations for all major platforms, including C++/Java/Python one published by Google itself.

As it was mention by Jon Skeet up above, PB spec does not define RPC model but it's extremely easy to define your own RPC using PB.

Alternatively, you could take a look at ASN.1. There is a ton of apps that use ASN.1.

blocks|key|401881|text|你可以看看ASN.1。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|401882|它用于在许多其他协议(例如SNMP、LDAP)中编码和传输二进制数据，尽管ASN.1本身并不定义传输协议。|401883|entityMap|0|LINK|mutability|MUTABLE|url|http://en.wikipedia.org/wiki/ASN.1^0|5|5|0|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@$A|O|B|P|1|Q]]|C|$]]|$1|D|3|E|5|6|7|R|8|@]|9|@]|C|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|C|$]]]|G|$H|$5|I|J|K|C|$L|M]]]]

You could look at <a href="http://en.wikipedia.org/wiki/ASN.1" rel="nofollow noreferrer">ASN.1</a>.

It's used for encoding and transmitting binary data in many other protocols (e.g. SNMP, LDAP) although ASN.1 does not itself define a transport protocol.

blocks|key|734670|text|Joe的UBF似乎还没有流行起来，但是它通过一个有品位的设计满足了您的需求。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|734671|entityMap|0|LINK|mutability|MUTABLE|url|http://www.sics.se/~joe/ubf/site/home.html^0|4|3|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Joe Armstrong's <a href="http://www.sics.se/~joe/ubf/site/home.html" rel="nofollow noreferrer">UBF</a> doesn't seem to have caught on, but it satisfies your requirements with a tasteful design.

blocks|key|735003|text|我建议试用RabbitMQ+AMQP，并使用协议缓冲区、XML或其他数据格式(如JSON+)来体验。除了相对简单和容易开始之外，这还允许您混合和匹配RPC和异步pubsub样式，并且在语言、协议和平台上有很好的扩展。但这可能不适合你的问题--这完全取决于你想做什么！干杯，亚历克西斯|type|unstyled|depth|inlineStyleRanges|entityRanges|data|735004|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I would recommend trying out RabbitMQ AMQP, and using Protocol Buffers, XML, or some other data format such as JSON, to taste. In addition to being relatively simple and easy to get started with, this lets you mix and match RPC and asynchronous pubsub styles, and has a good spread across languages, protocols and platforms. But it may not be a good fit for your problem -- it all depends what you are trying to do! Cheers, alexis

blocks|key|735058|text|有一个补丁，从ZeroC到冰，以支持谷歌协议缓冲区本机。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|735059|http://www.zeroc.com/labs/protobuf/|offset|length|735060|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|Z|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

There is a patch from ZeroC to Ice to support Google Protocol Buffers natively.

<a href="http://www.zeroc.com/labs/protobuf/" rel="nofollow noreferrer">http://www.zeroc.com/labs/protobuf/</a>

blocks|key|735070|text|风味风味，用于定义MPEG-4|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|735071|entityMap|0|LINK|mutability|MUTABLE|url|http://flavor.sourceforge.net/^0|2|D|0|0^^$0|@$1|2|3|4|5|6|7|L|8|@]|9|@$A|M|B|N|1|O]]|C|$]]|$1|D|3|-4|5|6|7|P|8|@]|9|@]|C|$]]]|E|$F|$5|G|H|I|C|$J|K]]]]

Flavor<a href="http://flavor.sourceforge.net/" rel="nofollow">Flavor, used to define MPEG-4</a>

I'm trying to find a suitable protocol middleware for my next distributed application. I've found several specifications in the last few days and was wondering if I missed an important one? It should be a binary protocol, support RPCs and optionally have open-source implementations in different languages. Here's the list of protocols I found:

<ul>
<li>CORBA</li>
<li>ICE</li>
<li>AMQP</li>
<li>Thrift</li>
</ul>

And this is the list of dismissed protocols:

<ul>
<li>XML based protocols because they are text based (XML-RCP, SOAP, hand-rolled, etc.) </li>
<li>Protocol Buffers (Closed Source)</li>
<li>COM (Windows-only)</li>
</ul>

general-purpose binary protocols

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

教程

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云智能顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

EdgeOne AI 安全实战专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋

腾讯云AI代码助手

云原生构建

TAPD 敏捷项目管理

Cloud Studio

SDK中心

API中心

命令行工具

功能1上新10个字符

功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符功能2描述100个字符。

功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符功能2上新100个字符。

功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符功能5描述100个字符

功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符功能5上新100个字符

功能4上新

文章&问答评论现已支持表情

全新交互，全新视觉，新增快捷键、悬浮工具栏、高亮块等功能并同时优化现有功能，全面提升创作效率和体验

社区富文本编辑器全新改版！诚邀体验～ 

精选全网热门MCP server，让你的AI更好用 🚀

💥开发者 MCP广场重磅上线！

涵盖代码开发、场景应用、自动测试全流程，助你从零构建专属AI助手

一站式MCP教程库，解锁AI应用新玩法

聚焦“写作效率、视觉美观与运行性能”三方面进行全面升级，为您提供更高效、稳定的创作环境

社区富文本&Markdown编辑器全新改版上线，欢迎大家体验!

诚挚邀请您参与本次调研，分享您的真实使用感受与建议。您的反馈至关重要，感谢您的支持与参与！

社区新版编辑器体验调研

我正在为我的下一个分布式应用程序寻找合适的协议中间件。在过去的几天里，我找到了几个规范，并且想知道我是否错过了一个重要的规范？它应该是一个二进制协议，支持RPC，并且可以选择使用不同语言的开源实现。下面是我发现的协议列表：CORBA冰AMQP节俭以下是被驳回的协议清单：基于XML的协议，因为它们是基于文本的(XML、SOAP、手摇等等)协议缓冲区(封闭源)COM (仅限Windows)

问通用二进制协议
EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问通用二进制协议EN

回答 9

Stack Overflow用户

Stack Overflow用户

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问通用二进制协议
EN