Will we support Object JSON serialize?

[SunFulong]

First of all, I know a JSON text can be object or ARRAY, and we choose ARRAY way.

But, when I trying to develop with AWS WebSocket API, AWS only support explain property of OBJECT as route key.

So, will we support the OBJECT way serialize?

[oberstet]

I don't understand the question: every single element of args can be an object, the whole kwargs must be an object. So just serialize your object and put it into the right item ...

[KSDaemon]

@SunFulong If you mean that the whole WAMP message can be an object instead of an array as it is now — sorry, noway.

[SunFulong]

OK, thank you for your firm answer, I should make a WAMP-like protocol for AWS.

[oberstet]

yes, true. it wouldn't make sense (it would be a different protocol), and it is not needed

[SunFulong]

The only sense is: it will be compatible with AWS WebSocket API Gateway.

[oberstet]

Or, you could use a proper, more powerful and likely cheaper WebSocket gateway like Cloudflare.

[SunFulong]

Or, you could use a proper, more powerful and likely cheaper WebSocket gateway like Cloudflare.

Could you give me a link? I didn't google it out

[ecorm]

If you're going to adopt the AWS ecosystem for your project, they may already have something similar to WAMP you could adopt. I am not familiar with the AWS tech stack.

If the idea of adopting WAMP is not to be tied to a vendor's proprietary tech stack, perhaps you could add an intermediary layer that wraps the WAMP array message into an object?

[SunFulong]

perhaps you could add an intermediary layer that wraps the WAMP array message into an object?

Yes, I will wrap the ARRAY-JSON message to OBJECT-JSON message, for each element add the NAME key describes in spec, e.g. {message_type: 1, realm: "somerealm"}

If you're going to adopt the AWS ecosystem for your project

No, not ecosystem, only their SAM (Amazon Serverless Application Model). I put a root WAMP router on SAM, and connect our IDCs via WAMP (like) protocol, each IDC have an edge WAMP router and multiple business clients.

[ecorm]

I believe this wrapping approach would be called the Envelope Wrapper pattern, if you're looking for a name: https://www.enterpriseintegrationpatterns.com/patterns/messaging/EnvelopeWrapper.html

[SunFulong]

Looks like, but not, because I didn't unwrap the message back to raw, instead, process the wrapped message directly.

[oberstet]

However you call the resulting mess, please don't call it WAMP ;)

[SunFulong]

However you call the resulting mess, please don't call it WAMP ;)

Yes, I won't call it WAMP, but will in my document write "foo protocol - a WAMP like protocol"