缺少 AMQP v.1.0 交换定义
我正在阅读有关 AMQP 0-9-1 实现的 RabbitMQ 规范，并按照教程页面中的示例进行操作，这些示例有助于解释交换和队列。 AMQP 规范 v.1.0 的最新主要版本已经发布两个月了，根据此 wikipedia 文章 Exchange/fanout/direct/topic 绑定的定义已被删除。以下是 AMQP v1 的完整规范.0。
我一直在阅读完整的 v1.0 规范，但它的技术性很强，并且没有对如何在生产者和消费者应用程序等场景中使用它的一般解释，或者它与 0-10 有何不同以及如何关联旧的与新概念的绑定和交换。
所有这些 Exchange 功能如何适应新协议。如果有一些 lib 实现的示例用法和代码示例，那将会很有帮助。
I was reading RabbitMQ specification on the AMQP 0-9-1 implementation and followed along the examples from the tutorial page which were helpful on explaining Exchanges and Queues.
The new latest and major release of the AMQP spec v. 1.0 has been out for two months and according to this wikipedia article the definition of Exchange/fanout/direct/topic bindings have been removed. Here is the full spec for AMQP v1.0.
I've been reading the full v1.0 spec but it's very technical and has no general explanation of how it can be used in a scenario for example a Producer and consumer application or how it's different from 0-10 and how to correlate the old Binding and Exchange notion to the new one.
How does all this Exchange functionality fit in the new protocol. If there are example usages with code example of some lib implementation that would be helpful.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
当前状态的 AMQP 1.0 没有指定代理行为（即代理如何处理和分发消息），仅指定 AMQP 网络中的 2 个节点如何在它们之间进行自我通信。有一个名为“代理行为”的草案文件旨在指定该领域，但它还处于非常早期的阶段，因为到目前为止大部分 1.0 活动都集中在核心协议规范上。所以你可以说，在某些方面，1.0 的规定比旧的 0.x 版本要少得多。
因此，在规范的“代理行为”部分至少达到一定程度的成熟度之前，很难想出相当于 1.0 的示例发布到交换并订阅它，因为不同的 amqp 1.0 实体可能以完全不同的方式实现它。许多 amqp 供应商可能会在他们的 0.9 产品中实现类似的行为。例如，RabbitMQ 实验性 1.0 实现提供了对其现有 0.9 代理的 1.0 访问权限。但这只是我的猜测。 以下是我对 AMQP 1.0 当前状态的一些其他想法< /a>
AMQP 1.0 in its current state does not specify broker behavior (i.e. how brokers handle and distribute messaages), only how to 2 nodes in AMQP network communicate between them self. There is draft document named "Broker behavior" that is intended to specify this area, but it is in very early stage since most of the 1.0 activity up to now has been concentrated around core protocol specification. So you could say that in some regards, 1.0 specifies much less than old 0.x versions
So until "Broker behavior" part of the spec reaches at least some maturity, it would be hard to come up with 1.0 example that would be equivalent to publishing to exchange and subscribing to it, since different amqp 1.0 entities could implement it quite differently. Probably, many amqp vendors will implement similar behavior to their 0.9 products. For instance RabbitMQ experimental 1.0 implementation provides 1.0 access to their existing 0.9 broker. But that is just my guessing. Here are my some other thoughts about current state of AMQP 1.0