Session: Difference between revisions

From Tygron Preview Support Wiki
Jump to navigation Jump to search
No edit summary
No edit summary
Line 7: Line 7:


A session can be interacted with by multiple users at the same time. A session will generally be shut down once all users have logged out of the session. However, when chosen, a session can also be kept alive for longer periods of time.  
A session can be interacted with by multiple users at the same time. A session will generally be shut down once all users have logged out of the session. However, when chosen, a session can also be kept alive for longer periods of time.  
There are several reasons to keep a session alive:
 
There are several reasons to keep a session alive:
* The user has to wait on a result of a long computation.
* The user has to wait on a result of a long computation.
* The project acts as a web service, such as WFS or WMS and can be updated in the mean time.
* The project acts as a web service, such as WFS or WMS and can be updated in the mean time.

Revision as of 11:24, 4 October 2022

A session is a means for interacting with Projects in the Tygron Platform. A session has several stages:

  • Project startup phase, in which the project is initiated into computer memory.
  • A live phase, in which the user can interact with the project.
  • A save phase, in which the project data is stored from memory to hard disk.
  • A close phase, in which the session's processes are neatly terminated and the session's data is removed from memory.

A session can be interacted with by multiple users at the same time. A session will generally be shut down once all users have logged out of the session. However, when chosen, a session can also be kept alive for longer periods of time.

There are several reasons to keep a session alive:

  • The user has to wait on a result of a long computation.
  • The project acts as a web service, such as WFS or WMS and can be updated in the mean time.

The interaction possible with a session can be restricted, based on the chosen startup mode.

  • Editor mode allows users to adjust the initial state of a project. Additionally, test-runs can be activated within this session to test future scenarios. Restrictions concerning test-runs in editor mode can be found here.
  • Single and multi-user mode allows users to only adjust the future state of a project. The initial state will remain the same, and indicators and overlays can refer to this initial state to show the improvements and progress being made.

Editor Test Runs