In each workspace's properties, there is a "minpool" setting which determines how many workspaces are "spun up" (pre-loaded) for immediate use by incoming web client requests, so users don't have to wait for a fresh interpreter and workspace to be started before their request can be serviced. This works great for quick individual requests, but isn't as beneficial when making use of the one-on-one feature.
If I've set minpool=1 so that a workspace is always available for an incoming request, and that workspace is then assigned to a particular one-to-one client, then a fresh workspace is no longer available if a new client comes along with a request of their own, forcing them to wait for a new instance of APL to be available.
Therefore, I would like to request a simple enhancement by way of an adjustment to the minpool definition. I think that minpool should be defined to be the minimum number of available server instances over and above any currently reserved one-to-one sessions.
That way, any time an APL session is assigned one-to-one to a client, a new workspace would then be spun up and available for immediate use by any new client that might happen along during that time. When a one-to-one session is released, then the pool of instances can be reduced after the usual timeout back to the current minpool.
This adjustment may be as simple as adding in a single extra number when making the minpool count check. Might there be programming resources available to make a simple change like this in the next month or two?