Although I don't see how that method maps to a URL that can be accessed by iviewer?
Even when microservices are not deployed, users may wish to configure a limit on active channels. This could (should) be a new server-side configuration (allow it to be accessed via the rendering engine itself as well as other clients.
When using the
omero-ms-image-regionmicroservice, the number of active channels is limited by default to 10 (configurable at https://github.com/glencoesoftware/omero-ms-image-region/blob/a3c6e61ecb02c608f4c1f8c296c259d7de9f5cc3/src/dist/conf/config.yaml#L12)The limit can be queried at https://github.com/glencoesoftware/omero-ms-image-region/blob/master/src/main/java/com/glencoesoftware/omero/ms/image/region/ImageRegionMicroserviceVerticle.java#L486
Although I don't see how that method maps to a URL that can be accessed by iviewer?
Even when microservices are not deployed, users may wish to configure a limit on active channels. This could (should) be a new server-side configuration (allow it to be accessed via the rendering engine itself as well as other clients.