Scripting/FlowControl
De DigiWiki.
(Page créée avec « Understanding the Code Flow of Aurora Due to the largely asyncronous nature of Aurora, the code flow of Aurora is quite complex and has many paths. However, all start out f… ») |
|||
| Ligne 1 : | Ligne 1 : | ||
| - | Understanding the Code Flow of Aurora | + | '''Understanding the Code Flow of Aurora''' |
Due to the largely asyncronous nature of Aurora, the code flow of Aurora is quite complex and has many paths. | Due to the largely asyncronous nature of Aurora, the code flow of Aurora is quite complex and has many paths. | ||
| Ligne 6 : | Ligne 6 : | ||
The only difference between Aurora.Server.exe and Aurora.exe is what modules that each load (you can make Aurora.Server start regions if you try). | The only difference between Aurora.Server.exe and Aurora.exe is what modules that each load (you can make Aurora.Server start regions if you try). | ||
| - | 1): During Startup, the Application starts off with loading the configuration options from the commands passed into it by the application that started it. | + | 1) : During Startup, the Application starts off with loading the configuration options from the commands passed into it by the application that started it. |
| - | 2): It then reads the basic configuration files (.ini files) and sets up the error/crash reporting and logging utilities. | + | 2) : It then reads the basic configuration files (.ini files) and sets up the error/crash reporting and logging utilities. |
| - | 3): It loads the ISimulationBase, which begins the main process of staring the Standalone, and it loads the ICommandConsole interface first, so that the console is fully loaded. | + | 3) : It loads the ISimulationBase, which begins the main process of staring the Standalone, and it loads the ICommandConsole interface first, so that the console is fully loaded. |
4): It then lets the IApplicationPlugins take over, which begin the loading of the IService modules and the AuroraDataPlugins, which connect to the database and establish connections as necessary. | 4): It then lets the IApplicationPlugins take over, which begin the loading of the IService modules and the AuroraDataPlugins, which connect to the database and establish connections as necessary. | ||
