You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 8, 2021. It is now read-only.
Regardless of the machines listed in the machine configuration file, we need a way to specify the number of allowable concurrent sessions to use for a Remotely call. The main requirement is a way to explicitly force Remotely to use a single session for the call rather than returning an array of session results.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Regardless of the machines listed in the machine configuration file, we need a way to specify the number of allowable concurrent sessions to use for a Remotely call. The main requirement is a way to explicitly force Remotely to use a single session for the call rather than returning an array of session results.
The text was updated successfully, but these errors were encountered: