Konstantin Burkalev

I'll remove `needs consensus` as seems most of all agree with the proposed solution.

Decided to take a run at this again as I think it is one of the easy-to-implement and at the same time yet powerful features, that gives future extensibility for ...

> Was it already discussed whether the router should propagate these custom attributes when doing CALL -> INVOCATION and YIELD -> RESULT? All I can remember — is the discussion...

Yeah. Agree. So if a router doesn't understand custom attributes — it should not discard them but instead just forward them to other peers. It is okay if only the...

@konsultaner Well, seems that you messed it all a bit :) As @oberstet is on `subscription_id` side and not on `topic` one :) For subscription-based history, we do not need...

Read spec, this thread, related crossbar docs once again and still have no final thoughts how it should be done %)) So, here is a new portion from my side:...

And for me personally looking at event history from the publications side seems to be more straight forward: it doesn't matter how many subscriptions are there: exactly same uri, a...

Hey folks! Everyone who is participating in this discussion is welcome to PR https://github.com/wamp-proto/wamp-proto/pull/428. I tried to accumulate and order all discussions into specification text.

Closing it via #428 PR

Well, I think that as there are no tests for current `payload transparency` and there are already implementations aligned with spec, should we put efforts into creating tests for the...