Suggestion: Do not use "amqp" in the library name

[kjnilsson]

Nice work.

As far as I can see this library doesn't implement the ratified AMQP version (1.0) but instead the legacy version (0.9.1) that RabbitMQ uses. I suggest renaming the library not to include a mention of AMQP to avoid confusion.

RabbitMQ is pretty much the only message broker that still uses the legacy version of the protocol which means it can pretty much be considered a proprietary protocol of RabbitMQ.

[michaelklishin]

Therefore it can be one of

1. amqp091-rust similarly to https://github.com/rabbitmq/amqp091-go
2. A variation on various species of rabbits, or the word "rabbit" in various languages
3. rabbitmq-rust-client or something like that

[gftea]

changing the name is troublesome now since we have release v1.0 and it is used in production.
I would add info in readme that it is for 0-9-1 protocol

[cdbennett]

I see the point of this suggestion, it's valid. But some of the suggested names are cumbersome. At least 'amqprs' is short and the crate name matches the module name you refer to in Rust. Also it seems quite clear from the crate description that it's for RabbitMQ and AMQP 0-9-1 (from crates.io search result) so I doubt anyone is going to think it's for AMQP 1.0:

[github-actions]

This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 5 days.