Emile Cormier

> The archives on GitHub are different and there are no published checksums for those. That's why I raised this issue. I should have made that clearer in my description.

For an HTTP server parsing the request-target, is it sufficient to call [parse_uri_reference](https://www.boost.org/doc/libs/release/libs/url/doc/html/url/ref/boost__urls__parse_uri_reference.html) once, and then use the various `url_view::has_*` methods to verify that the URL belongs to one of...

In the absence of the docs proposed in this issue, I have cobbled together some functions to validate a request-target URL within an HTTP server. If you don't mind, please...

> Sounds good. Yes, I know the two implementations. However, they are both not header only. @rggjan, msgpack-c is indeed header-only if you use the C++ API

I'm facing this same dilemma in my C++ router implementation and will be adopting GregRos' suggestion.

> One question here that came into my mind: if we go both way may some wamp client/router implement only one variant? Should it be treated and announced as supported?...

I think the router should propagate a custom attribute, unless it understands it and knows it's supposed to consume it without propagation.

It's not clear if IDs above "Session Scope" only need to be unique under a given realm, or if they need to be unique across a router hosting multiple realms....

> Also, what is the rationale for PUBLISHED.Publication and EVENT.Publication needing to be random? Found this Google Groups thread and linking it here: [why is Publication ID drawn randomly?](https://groups.google.com/g/wampws/c/jQc-L1yrUU4) I...

> then the dealer has to maintain a running timer for every pending RPC from all clients. Wouldn't that scenario hurt performance and scalability on the dealer side? I'm implementing...