Elad Zelingher

If you register your procedures with DiscloseCaller=true, you can access the AuthenticationId (the string set by your authenticator) by WampInvocationContext.Current.InvocationDetails.AuthenticationId. If you store somewhere the token used by the client...

I have another idea - your authorizer can check if the token is valid in its CanXXX methods. Elad

I think that the desired behavior is to allow checking whether the client is allowed to receive an event, and to allow to drop the connection (also in the previous...

Sounds like a nice idea. I am for it. Elad

The `SupportsCancellation` property was designed for remote callees, I never thought about the usage of registering such procedure in the RpcCatalog directly. I guess the easiest fix would be to...

So actually it turns out that cancellation is not supported for operations registered using the Catalog directly. The `WampRpcOperationCatalog` is sort of an internal implementation detail that should not be...

Can you explain your usage of the raw callee interface? Why can't you use the reflection based callee? Maybe I can design a nice feature for scenarios similar to yours....

You can use a CalleeInterceptor which allows you to customize the procedure name. >

Leave it open, I'll think about what I want to do with it.

This has been considered in the past and wasn't implemented as it is too vulnerable. I am open to ideas how to implement this in a way that doesn't put...