Liangying.Wei

In general, when you have the connection string you can use all the features the service provided, for example, connect to the service, call the REST API of the service...

> Since User is optional when creating a token I really find it hard to understand why this flow is mandatory. I think the main responsibility of this workflow is...

> How does code like this actually help to prevent that? Ah, that one is a simple demo to show some basic idea, a more real-world case would be your...

> What I really want is to not have a middleware May I ask the reason for not having a middleware? Don't want a long-run server-side? Want one service to...

Thanks for the feedback. Do you have some scenarios for such metadata, for example, can clients edit such metadata or should it be readonly to the clients? `ConnectionContext` contains the...

Yes, the feature makes total sense to me. The concern of adding the metadata to `GetClientAccessUri` is that it actually sets the info inside the jwt token which then is...

set `state` is now available in https://www.npmjs.com/package/@azure/web-pubsub-express/v/1.0.0-beta.3 Sample usage: ```js const handler = new WebPubSubEventHandler("chat", ["https://xxx.webpubsub.azure.com"], { handleConnect(req, res) { // You can set the state for the connection, it...

using `az webpubsub service broadcast `

maybe rename from `broadcast` to `sendToAll` to be consistent with REST API and SDKs

Yes, this is doable using multiple instances. Please do contact our support team if you'd like further technical support. You can also directly contact our product team through `awps(at)microsoft.com`.