Elad Zelingher

Here, read [this](https://stackoverflow.com/a/21716654).

Actually all connections need to terminate upon a serialization error (and a few other errors). For now we should mimic the JSON/text behavior. I'll try to make serialization exceptions terminate...

I'm sorry, I misread the issue. I thought only the binary version has the issue. In this case, I think we should catch the exception and close the connection. It...

Hi Michael, It is not possible for callers. For callees this is done automatically by mapping keyword arguments to the arguments with the same names. Note that positional parameters have...

Hi, I prefer having an attribute indicating whether the whole arguments are positional or keywords. (Otherwise it might get too complicated) Regarding callees: If you have a method [WampProcedure("com.example.keywordsexample")] object...

Hi @Chunky-Monkey, I never implemented such feature. As stated above, I support adding an attribute which indicates whether all arguments should be treated as keyword arguments/positional arguments.

I'm not sure I entirely understand the question, but one popular approach is to subscribe to the TopicCreated and WampTopic.SubscriptionAdded event handlers. In the SubscriptionAdded you have access to the...

A year has indeed passed. However, new features had been recently proposed to WAMP advanced profile which try to resolve these sort of problems. See [here](https://github.com/wamp-proto/wamp-proto/pull/262) and [here](https://github.com/wamp-proto/wamp-proto/pull/264). Elad

Hi Péter, Thanks for opening this issue. It is possible to implement this on the router side, but it will require writing a lot of code, mainly due to the...

Hi, This is not the first time someone suggests me to support a different serialization library. This is not straightforward at all, and I will show some examples. When we...