Implement a server side queueing process to facilitate control of the flow of PSoS calls. Queueing requests should allow developers to specify script priority and (hardware) resource requirements.
See the inspiration thread for this Product Idea:
Serial Script Execution and Logging as a stand-alone File
And…why limit it to PSoS? Why not have the option of channeling all server-side script execution into a serial-based Queue or "ad-Hoc", or — when defining the script to be executed by the client to "Server", choose to specify which server to explicitly process the script, or choose to send it to the first available dedicated server (If such a feature is ever made available for script execution)?
You got to be a lot more specific on how you expect this to work? High/Medium/Low priority. What if a Low priority is executed before there is a High triggered?
Don't use PSOS for that, use server side scripting, launched by an URL to a php files that triggers a fmsadmin command line code that launches the scheduled queue launcher script.
I've this setup for years, works like a charme, I've 3 queue launcher script to handle priority.
Works much better than PSOS, has no authorization problem when opneing files required by subscript, unlike PSOS, and also limits the strain on the server CPU.
Agreed, this is a stub of an idea from a discussion thread.
I added three other people from the original thread as co-owners of this idea so that they can contribute more specifics.
The thrust behind this to de less "rigging" of home-spun ideas that may be difficult to implement, or brittle, and to have FMI be the one to implement more core server functionality such as queueing, database replication, load balancing, etc.
Retrieving data ...