Fix: don't throw warning for unsubscribe results

[lmagyar]

Without waiting for the reply, it always created a warning: Received result for unknown message with ID: x

[marcelveldt]

Continuation of the other reply. Maybe we should not care and just log this to verbose. In nay case its not worth it to await the unsub reply unless I'm missing some usecase here.

Are you perhaps interested in doing sub+unsub during runtime ?
The usecase for me is just setup all subs at startup/connect and only unsub at shutdown/disconnect.

Maybe all this takes is a separation of the subscribe and unsubscribe, make them 2 individual functions and leave it up the caller to handle.

[lmagyar]

Yes, sub+unsub during runtime. :)

Hmmm, and how will the caller identify the subscription if it is a separete method? Currently the id is captured in the function, this is sooo elegant.

The only thing that bothered me, was the warning, if the warning is only a debug/verbose message, I'm fine with it.

[marcelveldt]

I was thinking of giving back the subscription ID so you can store that and decide for yourself if you want to unsubscribe.
But lets adjust it the other way and keep the ubsub function in the subscribe result but leave it as a "set and forget" task.
So ignoring the log is the goal.