HTTP API Plans

[clanofartisans]

I suspect this is mostly for @zach2good but I'm curious about the future of the HTTP API baked into the world server. Are there plans for how you want to expand it? I have a web developer background so it has me really curious and I might take a crack at adding to it but the possibilities are endless and I don't know what you had in mind.

[zach2good]

I don't have any active plans. It has its own thread/task system, it defines its own endpoints, and it defines an internal caching system. Like many things I do: I implement an extensible system and provide some examples in the hope that someone else will take interest and run with it in a sane direction.

So, suggest some things and see if they're relevant 👍

[clanofartisans]

One of the things that's been kicked around between me and @WinterSolstice8 is a way to reset sessions, preferably in a way that's player initiated. This would require some sort of authentication. I think you could get away with using HTTP Basic Auth (baked into httplib) for a couple endpoints here and there given that they'd be used rarely but, for anything more elaborate requiring authentication, I think you'd need something a little more robust. Something that could issue and manage tokens with expirations and such would be the sensible way to do that but that seems like it could add a lot to the scope of this API. Do I need to pump the brakes and focus on smaller things for now?

[cocosolos]

I'm making use of the API with https://ixion.dev (source). I don't have any experience with web dev so it's probably not great, but I wanted to experiment with the API. One thing I noticed is that unlike the other servers, it doesn't watch for changes to the settings files and can give outdated settings. Not really sure what else could be added though that isn't better suited to just directly accessing the DB.