celeron55/buildat
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

doc/whynot: Something about module instances

Browse Source
This commit is contained in:
Perttu Ahola 2014-10-26 13:03:14 +02:00
parent 3213a7f27d
commit e99f96b334
1 changed files with 9 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
doc/whynot.txt
View File

@ -9,3 +9,12 @@ Why not detect -DURHO3D_64BIT automatically in the build system?
Why not use cereal's versioning system? Why not use cereal's versioning system?
- It doesn't support forward compatibility - It doesn't support forward compatibility
Why not allow making arbitrary number of instances of any module?
- It would make module reloading and management practically impossible, and it
would make module interoperability much harder to achieve. Creating a robust
but usable system for threading is also tricky. Also, it does not make that
much sense to run multiple worlds in a single server process because then all
would crash if one crashes.
- Instead there should be easy mechanisms for launching new server processes at
runtime, and routing clients to different processes.