Hi Luis,

This is awesome, and just what I was currently engaged with Support about! Talk about good timing...

A couple of questions:

In your "broadcast" routine, you have the read of the Websocket in IRIS like:

Set data= ws.Read(, .status, )

The docs say that the format of that call is:

method Read(ByRef len As %Integer = 32656, ByRef sc As %Status, timeout As %Integer = 86400) as %String
 

Won't that mean that if your WebSocket is open (but the user is out to lunch), you will hang for 86400 seconds before returning?

Second, do you know what the licensing impact on IRIS is for this? Say there was 100 notification targets,. Would the system take out 100 License Units in this loop?

Thanks!

Richard

So now, it doesn't look like the request is ever even making it to IRIS.

We're using IIS 7 on a Microsoft Server, but I thought the request would be straight mapped to CSPGateway by IIS, but maybe I need to configure IIS not to reject the request as well?

I should also say that my Data Classes are inheriting from AppS.REST.Model.Proxy, and access via Postman works perfectly.