Konstantin Burkalev

I think it is ok. We follow SemVer, right? - Right. So I don't see any problem in sometimes breaking changes if that simplifies the logic and improves the project...

Hi @ialse sorry, this feature is not supported yet. But feel free to make an PR with the implementation ;) Your help would be highly welcomed!

Feature description: https://wamp-proto.org/wamp_latest_ietf.html#name-event-retention

Well... The `CALL` may be canceled on different sides. But in the context of the original question — i think that the peer should just check that dealer supports the...

O, thanks for description how it works under the hood > the problem is: the use of the specific subfeature CANCEL happens when the original CALL feature already is in...

Yeah! Lack of details in call results is an important issue. In Wampy.js for example, in all cases (event, result) I return all of them: ```js { details argsList argsDict...

I have a quick look at my implementations and can say that: * Wampy.js sends: * `wamp.close.goodbye_and_out` on receiving `GOODBYE` message from the router. * `wamp.close.system_shutdown` when disconnection is initiated...

my 50cents fwiw: * wampy.js uses only `wamp.close.goodbye_and_out` and `wamp.close.system_shutdown` * Nexus uses `wamp.close.normal`, `wamp.close.system_shutdown`, `wamp.close.close_realm`, `wamp.close.goodbye_and_out`

Well, interesting question! For example, in E2EE part, we have options to specify the encryption scheme; anyone can build its own scheme and use it. But we missed that for ...

> rgd starting a "real" IETF WG: we need a host/chair, but https://datatracker.ietf.org/person/Salvatore%20Loreto https://www.linkedin.com/in/salvatoreloreto/ some time ago told me he'd probably be willing to help! Oh that's cool! I'm +1...