A session in 1010data is an established period communication between the user and the system. Only one session per user may be active at a time.

In 1010data, a session refers to the period a user is connected to the system from the time they log in until the time they log out or have been logged out due to inactivity. Currently, only one session may be active at a time for each user account.

Sessions are an important part of 1010data's design, and they provide numerous benefits. First, sessions permit caching of operations. Whenever a user performs an operation in 1010data, that operation and its results are stored in the session's cache. This is done so that if the operation needs to be run again at a later time the results are already calculated and are accessible via the session cache. This design feature allows for a compositional, orderly approach to data analysis.

A session cache has physical limitations. Every account has a maximum amount of memory it is allowed to use for cached information and current processes. This limit is called the workspace.

When a user has an established 1010data session and attempts to login to the system via a different mechanism (e.g., another browser window or tab, a client-side tool like TenDo, etc.), you have the option to end the existing session and create a new one, or to re-enter the existing session. When done via the web interface, this presents the user with the following options at login:

Table 1. Possess a session options
Option Description
Re-enter existing sessions Choosing this option means the user doesn't have to login again and has access to the cache from the active session.
End existing session Choosing this option requires the user to login again. Once logged in the user has a brand new session and no operations or data in their cache.
Note: You cannot re-enter a session that was started via the 1010data API.