api
api copied to clipboard
feat(aoc): AOC Simulation (Part 1)
This PR is part of a bigger project to implement a full immersive AOC simulation.
Part 1 will consist of the following changes / additions:
- [ ] Implement AOC Connection Endpoints (POST - register, PUT - keepalive)
- [ ] Implement Telex functionality into AOC endpoints (freetext)
- [ ] Add Database Migration to migrate data from Telex Connections -> Aoc Connections & Telex Messages -> Freetext Messages
- [ ] Redirect Old Telex Message Endpoints
Part 2: Implement OOOI Endpoints Part 3: Implement Init Endpoints
This list is not exhaustive and subject to change.
Hey guys, wanted to start a discussion on this one. I think it would make more sense to move this away from the FBW API into the simbridge as it doesn't need any connectivity to other pilots or anything else (except the Telex / Freetext functionality - but for this one to keep it simple from the aircrafts perspective my suggestion would be to use the Simbridge as the bridge between the FBW API and the aircraft).
This would also lead to neither having to authorize a second time to the Navigraph services for any simbrief / navigraph related services nor to have any JWT tokens to be synced with an external API.
What are your thoughts on that? @tracernz @svengcz Feel free to tag anyone else who might have an input too.
I think it would be better not to depend on SimBridge as in it's current form it's quite performance heavy. I personally don't typically use it for this reason.