Emile Cormier

@oberstet , did you click "Comment and Close" instead of just Comment? Before closing this issue, perhaps we should wait until the feature announcement scheme is settled and that my...

> How could a Dealer provide `dealer.feature.subscription_meta_procedures = true` without there being a Broker? It shouldn't. Implementation-wise, some higher level entity would have "tell" the Dealer that `subscription_meta_procedures` are available...

A third scheme would like the one currently used by Crossbar, but we'd add a "router" role to announce generic features such as `session.meta.api`. But introducing a new "virtual" role...

There are two different issues being discussed here, and it's my fault for ^not^ separating them. The first is to update the Meta Api spec with what's been implemented so...

> What use case does feature announcement address again? It could be useful when consuming WAMP services from a 3rd party, where you have no control over the router and...

Submitted PR #180 for syncing the meta API spec to the one currently used by Crossbar.

We are using a C++ client (CppWAMP) for our backend which does not support the `INTERRUPT` and therefore does not include the `call_canceling` feature in its `HELLO.Details.roles.callee.features`. We are using...

@meejah Unfortunately, I'm working on something else not WAMP-related and won't have the chance to re-test anytime soon. When I switch back to WAMP mode, I'll let you know (and...

@meejah I forgot to mention that we worked around this problem by implementing INTERRUPT in CppWAMP.

The skip mode in [processCancel](https://github.com/crossbario/crossbar/blob/847138679831c963c8b313984e060883efa7f15e/crossbar/router/dealer.py#L1122) doesn't return an ERROR message back to the caller. This [block of code](https://github.com/crossbario/crossbar/blob/847138679831c963c8b313984e060883efa7f15e/crossbar/router/dealer.py#L1191) that returns an ERROR message is never executed for skip mode due...