Binary serialization/deserialization support; support for proxy

[SergeyFilippov]

As we're working with RabbitMQ by both AMQP and STOMP, it was required to add binary serialization support.
Also, we're mostly consuming existing queues, and current implementation would throw an exception in this case. It is still problematic to subscribe to existing queue - as RabbitMQ may use different paths, but it's not throwing an exception now :)

Here is the list of implemented improvements :

• binary serialization/deserialization
• existing queue subscription
• web proxy support
• hearbeat message type added
• nugets updated

[mael-app]

Hi @SergeyFilippov, according to my checks, the fact that connecting to a queue will inevitably ask to recreate it is caused by the STOMP protocol itself. I don't know if it's possible to bypass it through the library.
I'm trying to set restricted permissions for my user, but he's asking me for configure permissions as he's going to create it, which bothers me.

[SergeyFilippov]

Hi @SergeyFilippov, according to my checks, the fact that connecting to a queue will inevitably ask to recreate it is caused by the STOMP protocol itself. I don't know if it's possible to bypass it through the library. I'm trying to set restricted permissions for my user, but he's asking me for configure permissions as he's going to create it, which bothers me.

We're using this implementation in the app, and it works with the following scenario:

1. In the main app we're creating user and queue for a client
2. We're sharing connection information with client
3. Client is able to subscribe to existing queue and consume messages

I'm not sure what your scenario is, but I it's definitely possible to connect to existing queue using this client.