Probably we should make it simpler, instead of more complex:

• URIs on the wire are always fully qualified, never CURIEs
• the wire payload can be compressed, optionally, i.e. using transport compression like WS-deflate
• CURIEs can still be used -- purely peer side, implemented purely in peer library

from wamp-proto.

If CURIEs are only used on peer side (client javascript?), what advantage is there defining a CURIE instead of just using a variable, if it's not going to be sent on the wire? Would it make sense to remove Prefix/CURIEs all together?

from wamp-proto.

Good point. I guess it would mostly be a matter of taste. There are multiple ways to make URI handling convenient - client side.

I really think this issue boils down to 2 sane options:

• always have full URIs on the wire
• have all clients agree on a common prefix map for CURIEs and have CURIEs on the wire

The first one is straight forward.

The second one raises the question on how that agreement happens.

from wamp-proto.

I like simple. :)

from wamp-proto.

Yeah, me too. The concept of CURIEs seems somehow elegant, but the nitty gritty details in particular in the context of distributed PubSub (not so much RPC) are tricky.

I count that as 2 votes (you, me) to kick CURIEs from the wire protocol.

The Q of JS interface / URI convenience whatever is orthogonal .. can be done in AutobahnJS .. if at all.

from wamp-proto.

PREFIX message will be deprecated in WAMPv2.

from wamp-proto.

👍

from wamp-proto.

You guys are just removing a nifty feature of WAMP, making it appear lousier than STOMP over websocket.

from wamp-proto.

STOMP does not seem to provide builtin RPC features. The PREFIX message of WAMPv1 effectively only provides some adhoc, poor-man's compression. Using WebSocket compression, there seems to be no justification for PREFIX anymore.

from wamp-proto.

WAMPv2 has deprecated CURIEs altogether.

from wamp-proto.