... | @@ -28,19 +28,19 @@ I think that the second option is the most interesting, as it permits any module |
... | @@ -28,19 +28,19 @@ I think that the second option is the most interesting, as it permits any module |
|
|
|
|
|
## Annexe:
|
|
## Annexe:
|
|
|
|
|
|
Data Structure:
|
|
### Data Structure:
|
|
We thought about 4 different type of data which will be store differently.
|
|
We thought about 4 different type of data which will be store differently.
|
|
|
|
|
|
—>Persistent Data, (SAVE, LOG, Chat ?, IA(2nd way to play not the real one))
|
|
1. Persistent Data, (SAVE, LOG, Chat ?, IA(2nd way to play not the real one))
|
|
====== Most of this can be stored in a SQL Data base. which will allow fast and easy auto-save. (file might be consider too)
|
|
====== Most of this can be stored in a SQL Data base. which will allow fast and easy auto-save. (file might be consider too)
|
|
—>Semi-Persistent Data (Characters stats, …)
|
|
2. Semi-Persistent Data (Characters stats, …)
|
|
======Here we will store those information on SQL too, but the data will stay in cache as long as nobody requested it, as a module will eventually.
|
|
======Here we will store those information on SQL too, but the data will stay in cache as long as nobody requested it, as a module will eventually.
|
|
—>Volatile Data (Character HP, position, speed,acceleration).
|
|
3. Volatile Data (Character HP, position, speed,acceleration).
|
|
======Most of this information which need fast access will be in cache.
|
|
======Most of this information which need fast access will be in cache.
|
|
—>Map
|
|
4. Map
|
|
======According to us map, is very particular and should be deal with separately, we thought about XML or AXML.
|
|
======According to us map, is very particular and should be deal with separately, we thought about XML or AXML.
|
|
|
|
|
|
Discusion about solution 2:
|
|
### Discusion about solution 2:
|
|
|
|
|
|
It heavily depend on languages each sub module want to us. Few groups we were talking too, where up to do C++, if most of them would then it will easier our job.
|
|
It heavily depend on languages each sub module want to us. Few groups we were talking too, where up to do C++, if most of them would then it will easier our job.
|
|
However we are willing to offer to each sub-module his own library in the language he wants to be able to communicate to our module and so to every module. Such libraries would share data thanks to SQL,XML,and shared memory (mmap), to optimize speed, it will be in C/C++.
|
|
However we are willing to offer to each sub-module his own library in the language he wants to be able to communicate to our module and so to every module. Such libraries would share data thanks to SQL,XML,and shared memory (mmap), to optimize speed, it will be in C/C++.
|
... | | ... | |