You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
From their inception in Jan 2013, they have been one element in Bunny's approach to connection
recovery that I've always had doubted.
Bunny's connection recovery approach was ported to both Java and .NET clients, and has stood the test of time. However, version tagging specifically was not adopted by most Bunny-inspired AMQP 0-9-1 clients.
All other parts of Bunny's connection recovery are easy to reason about and explain, as years of experience with the RabbitMQ Java and .NET clients demonstrate. That's not the case with versioned delivery tags, which are not a protocol concept.
Removing versioned delivery tags is one of the low hanging simplification fruits.
The text was updated successfully, but these errors were encountered:
From their inception in Jan 2013, they have been one element in Bunny's approach to connection
recovery that I've always had doubted.
Bunny's connection recovery approach was ported to both Java and .NET clients, and has stood the test of time. However, version tagging specifically was not adopted by most Bunny-inspired AMQP 0-9-1 clients.
All other parts of Bunny's connection recovery are easy to reason about and explain, as years of experience with the RabbitMQ Java and .NET clients demonstrate. That's not the case with versioned delivery tags, which are not a protocol concept.
Removing versioned delivery tags is one of the low hanging simplification fruits.
The text was updated successfully, but these errors were encountered: