ScriptX.Services for Windows PC and multiple concurrent users
ScriptX.Services for Windows PC provides a web server on the local loopback address (127.0.0.1). Many software solutions do this and so each solution uses a unique port. The default configured port is 41191.
Port sharing is not allowed so this meant that prior to v2.15 if another user signed in ScriptX.Services would not start due to a port conflict.
ScriptX.Services for Windows PC v2.15 and later use dynamic port assignment on startup. This allows multiple accounts to be logged in to the PC at once and use ScriptX.Services as each user is assigned a unique available port.
This is one half of the problem solved but another created. Clients of the service must know which port to use for connection. Prior to 2.15 it could be assumed to always be a given port number and with 2.15 and later it still is if there are never concurrent signed in users.
We had two goals with the v2.15 release:
- Make it available to customers as soon as possible
- Require no changes to code using the ScriptX.Services Client library used to emulate ScriptX.Addon
The second goal was achieved with the simultaneous release of v1.9 of the library on Github. In this release of the library, when initialised with a URL to connect to, it tests the connection and if it fails then the port is incremented and connection tried again until a valid connection is found up to a maximum of 10 tested ports.
The significant issue with v1.9 of the library has been the poor performance experienced by users when a page is loading, especially if synchronous AJAX is used. There have also been issues with being unable to connect to the ScriptX.Services dashboard which while not often used is useful for problem troubleshooting.
The release of ScriptX.Services for Windows PC v2.15.5, v10.1 of the ScriptX.Services Client library and the addition of Orchestrator for ScriptX.Services for Windows PC addresses these problems.
For further information see the guide on Orchestrator.
Install Orchestrator along side ScriptX.Services for Windows PC and deploy v1.10.1 or later of the ScriptX.Services Client library if you have multiple concurrent users.