mysimulation/server
Tony Bark 22191ce648 Removed NioTSO client and server
- NioTSO client isn't needed because we're using RayLib
- Added FreeSO's API server to handle most backend operations
2024-05-01 02:55:43 -04:00
..
FSO.Server.Api.Core Removed NioTSO client and server 2024-05-01 02:55:43 -04:00
FSO.Server.Common Removed NioTSO client and server 2024-05-01 02:55:43 -04:00
FSO.Server.Database Removed NioTSO client and server 2024-05-01 02:55:43 -04:00
FSO.Server.Debug Removed NioTSO client and server 2024-05-01 02:55:43 -04:00
FSO.Server.Domain Removed NioTSO client and server 2024-05-01 02:55:43 -04:00
FSO.Server.Protocol Removed NioTSO client and server 2024-05-01 02:55:43 -04:00
tso.common Removed NioTSO client and server 2024-05-01 02:55:43 -04:00
README.md Removed NioTSO client and server 2024-05-01 02:55:43 -04:00
ZTSO.Server.sln Removed NioTSO client and server 2024-05-01 02:55:43 -04:00

API Server

zTSO utilizes the FreeSO API architecture for its backend, albeit not entirely compatible due to differences in simulation management.

Versioning Scheme

Instead of using FreeSO's versioning scheme, zTSO adopts a versioning pattern that adheres to SemVer guidelines with some modifications:

  • FreeSO version beta/update-88b becomes beta/update-0.88.101 in zTSO.
  • Prefixed letters in FreeSO version are replaced with a three-digit incremental patch number in zTSO, akin to .NET's SDK versions.

This versioning strategy aims to ensure that zTSO servers remain distinct from FreeSO-compatible servers while maintaining familiarity for existing users and server operators.