link is ugly af, but this alone saves 8 bucks per year in operating costs, and every saving that doesn't affect functionality only makes it easier to run this as a community project. With this in mind, and with the help of a few people in the Finnish server, I'm seriously planning to partially reengineer and restart the service using the domain il2missionplanner.link (no, it is not working at the moment, I just bought it for now). Please pass on my apologies and best wishes to them all. Also, if the community is curious what is going on, you can feel free to share any of our communications with them. I would suggest just reimplementing this feature yourself if you want it,įinally, it goes without saying, any code, images, etc. This technology was obsolete when I wrote it in 2016 has only gotten worse it does not work well, according to user reports. It is built using Redis and a Redis HTTP gateway called Webdis that uses HTTP Chunked Encoding to stream map updates. As for the streaming functionality, I would not try to fix that. This server is written in Go, but it is a very simple proxy to simply fetch various server owner configuration files and you could rewrite it in any language easily. From there, you can try to set up the API server to fix the import function. I think it makes a call when it loads to get the server list- you might just omit that and hopefully get the basic functions working again. My suggestion as a first step is to try to edit the javascript to not depend on the API. It is only required for importing server configurations and for the streaming functionality. The API backend is not necessary for the most basic planning functions.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |