The access token of this secondary DataSessionInterface.
Optional accesstokenextendedThe optional extended access token of this secondary DataSessionInterface.
The build properties of this secondary DataSessionInterface.
The time (in time_t) before a heartbeat may be performed for this secondary DataSessionInterface.
The end id for backend objects created from this secondary DataSessionInterface.
The proxy url id of this secondary DataSessionInterface.
The sequence start for backend object created from this secondary DataSessionInterface.
The secondary id of this secondary DataSessionInterface.
The start id for backend objects created from this secondary DataSessionInterface.
The SecondaryDataSessionInterfaceInfo interface is used to create secondary sessions of a given DataSessionInterface.
This is an opaque readonly object that may be streamed and read. Any modification of this object will result in undefined behavior. The SecondaryDataSessionInterfaceInfo is created with DataSessionInterface.requestNewSecondaryDataSession and used with DataSessionInterface.openSecondaryDataSession in replacement of DataSessionInterface.openDataSession.
There is only a finite number of secondary data session that can be created at the same time, ths it is necessary to call DataSessionInterface.unregisterSecondaryDataSession to notify the primary DataSessionInterface that this secondary data session is no longer in use (there is no internal signaling). It will be necessary to call DataSessionInterface.setTokenValues on a regular basis to notify the secondary DataSessionInterface of bearer modifications (use DataSessionInterfaceSignal.TokenUpdated for this matter).
or asynchronously :
The primary/secondary mechanism may be used to share the same DataSessionInterface across multiple tabs.