In parallel with updating 1on1 online webcam
Once the application updates have been completed, the sequencer user stops monitoring and the sequencer will process all the updates. Once the sequencing is completed, all of the new package files are copied up to the content share.
The Shortcut Wizard is then re-run, reconfirming that the application still works in Soft Grid. The sequencer will recognize that this package is an update and append an underscore and an increment number to the SFT files (e.g., EXAMPLEAPP. Next, the Soft Grid administrator adds a new Package version into the Soft Grid Management Console, referencing the new SFT file.
Also, no desktop refresh is required for this update, as it’s done on the SFT file that is being launched by the users.
The primary consideration for this method is that both the existing version and new version cannot be served to users simultaneously.
The first application update method is called Active Upgrade.
In this configuration, the existing package is copied down to a sequencer workstation.
The user simply launches the application and they are presented with the most up-to-date version of the application.
Since the application’s SFT is updated, the GUID stays the same, which means all machine and user settings are still associated with the applications are retained for users.
This creates an entirely new package that represents the updated version of the application.
The new package file is then copied to the content share and the Soft Grid administrator adds a new application record for this package.
The primary advantage of this method is that the upgrade can be run simultaneously with the existing version.
You might want to mention Python 3 first, as it's probably more future-proof.
In the current Soft Grid implementation, there are three distinct methods of providing users with an updated version of an existing Soft Grid application.