Doloro GDK 22 .1.0 Beta
by Tauri Interactive
|
Entire session data of storages and its connected stored within StoragesDatabase
singleton database instance.
The data could be serialized to binary view to save for continue cross-session using.
Explore API: Doloro.InvetorySystem.StoragesDatabase
Storage database entities should be operated via the Storages Service.
Normally entire database task encapsulated for you, but since you may need to extend its logic you better to understand from which parts the StorageDatabase
built.
StorageContainer
represents content of a Storage
entity that holding cross-session data.
Operates several child registries:
AStorageFeature
binary data, that represents state of features applied over Storage
instance during last rent session.ItemContainer
collection, that represents items metadata related to the storage instance.StorageContainer
bonds with the Storage
rented instance and updates in two cases:
Explore API:
ItemContainer
represents data that describes Item
state, to share it cross-session.
Stores:
AItemFeature
states found over rented Item
instance.Explore API:
FeatureContainer
is a data base entry that stores state of any EntityFeature
places into it by SaveSession
command.
Explore API: