Connection with another server?

[Reisen-Wandern-Tauchen]

Hey Reese,

it's me again, with another question... 🤣🤷‍♂️

I tried to connect my productive FSD server with an openFSD testing instance via the producive server's telnet interface.
In the first step it seems like the connection works, but taking a look in connections-list on my productive server is telling me, that the connection with the openFSD instance is pending.

Did you implement that functionality in principle? If so, is there anything I need to take into consideration?

Sorry to bother you again... I'm asking, as my initial plan was to use the other FSD server instance for all different status queries and to access it's whazzup.txt file for processing.

If establishing a connection with another server is not implemented, is there a way to query some status information from the server like the telnet interface on the very old original FSD server had? (could be a telnet interface, an API or whatever else... I just need to be able to get some information about the clients connected with the server 😉)

[renorris]

Hi Reisen,

No worries—feel free to keep asking any questions you may have. The only thing I can't guarantee is response time!

There is no multi-server implementation as of yet. Unless you're serving thousands of clients concurrently, this shouldn't pose much of an issue. There is, however, an opportunity to increase reliability / redundancy with a multiple-server setup. I will add it to the TODO list.

I'm currently working on a significant refactor across the entire project. This should yield more informative error reporting: hopefully answering the mysterious "ghost" syntax error message you observed in swift. The HTTP internals & front web interface will also be significantly improved. I will definitely add a whazzup.txt-esque API to the list.

[Reisen-Wandern-Tauchen]

No pressure 😉
The API sounds good. So I will patiently wait for it then 🥳

Thanks for your quick response. And don't worry. I won't kill me if I have to wait a bit for an answer. Same on my side as well. Sometimes life's just busy.

[renorris]

Hi Reisen,

I've just pushed the first commit for the new version I was referencing before. I plan to continue working on it over time, but for now you will find a VATSIM-esque data feed API accessible from the HTTP server, as well as some other additions. Most of the details should be in the new README. Let me know if you have any problems.

Reese

[Reisen-Wandern-Tauchen]

Hey Reese,

that's amazing! I will take a deeper look at it over the next days and the weekend. Sure I will let you know my feedback anyway.
Thanks a lot for all your effort!

Chris

[renorris]

No problem. I hope you get some good use out of it! If you're a vPilot user, I'll also link this just in case.

[Reisen-Wandern-Tauchen]

Just testing yesterday and today. The datafeed is working well and sim-connections seem to be fine as well so far.
Thanks for the update! And sorry for coming back so late. I had some personal stuff to take care of the last weeks so I couldn't test earlier...