title: Disconnecting in a publish subscribe situation with easynetq
body: <p>Currently I'm building some software with Easynetq (a .net lib ontop of rabbitmq). This works great except for 1 thing. </p>
  
  <p>We have a publish subscribe setup. A server pushes messages to a client that can or cannot be connected. In a unwanted scenario, the client could loose its connection. When the application closes you will do an unsubscribe so then the subscription is gone. But lets say the network connection is down. Is there any way to ensure that those messages are not processed? Or can we purge the messages on the OnConnect event? </p>