Signal sent by the DataSessionInterface when the DataSessionInterface has encountered an error while loading the DMU, i.e. after DataSessionInterface.openDataSession has been called.
The attachment is a string describing the reason for the error.
Signal sent by the DataSessionInterface when the DataSessionInterface has finished loading the required DMU, i.e. after DataSessionInterface.openDataSession has been called.
A this point, the user can create filters, search in the DMU, etc....
No attachment for events of this type.
Signal sent by the DataSessionInterface when the DataSessionInterface has finished cleaning the client and server resources. It may happen that the server resources have already been cleaned (by an idle time for example), in this case, the signal is emitted right after the client resources have been cleaned.
No attachment for events of this type.
Signal sent by the DataSessionInterface when the data session has already sent the IdleWarningDataSession event, and the user has interacted with the application (performing a metadata filter request) or DataSessionInterface.restartIdleTimer has been called.
No attachment for events of this type.
Signal sent by the DataSessionInterface when the data session has already sent the IdleWarningDataSession event and the DataSessionInterface has been closed on the servers. There is no possible recovery when the IdleDataSession event is fired.
Warning : at this point no cleanup has been done on the client side (only server side cleanup has already been done). You MUST call DataSessionInterface.closeDataSession to cleanup up the client resources.
This behavior is done to allow the application to show a message on top of the 3D before the actual 3D cleanup (if relevant).
No attachment for events of this type.
Signal sent by the DataSessionInterface when the user has been idle for a long time and the data session will be closed shortly after. If the user moves shortly after, nothing is done. You may cancel the idle behavior by calling the DataSessionInterface.restartIdleTimer function.
No attachment for events of this type.
Signal sent by the DataSessionInterface when a token has been refreshed.
This signal is sent when the data session bearer (DataSessionInterface.getDataSessionBearer), or extended data session bearer (DataSessionInterface.getExtendedDataSessionBearer) is updated. There is no information on the type of the token updated, it is the application responsibility to call DataSessionInterface.getDataSessionBearer, DataSessionInterface.getExtendedDataSessionBearer to know the new values of the bearers.
No attachment for events of this type.
Signal sent by the DataSessionInterface when the DataSessionInterface has created a new WorkingSet. There is no WorkingSetDestroyed signal since the only way to remove a WorkingSetInterface is to dispose it with WorkingSetInterface.dispose, and the InfiniteObjectDispatcherInterfaceSignal.ObjectDisposed signal is called on the object.
The attachment is a string that contains the id of the new WorkingSetInterface.
The DataSessionInterfaceSignal lists all the signals that may be sent by the DataSessionInterface.
These signals are emitted by the DataSessionInterface when :
The data session is opened following the given sequence :
The idle system is in charge to close the database after a while when no user interactions have been detected. It is composed of three pseudo-states : * Normal : the user is interacting regularly with the system. * Warning : the user has not interacted with the system from some time (2/3 of the idle duration as configured in the architecture). * Idle : the server resources have been cleaned up, the session is closed with no possibility to resume or recover. This state happens after the "warning" state.
The idle system.
Please refer to the DataSessionInterface for more information.
See
DataSessionInterface