I know that these changes are pretty big, but I thought that they'd be worth sharing. We have multiple dynmaps distributed across multiple virtual servers on the same machine. Currently, Dynmap-Multiserver doesn't support multiple servers, only multiple dynmaps on the same server.
I refactored some stuff and made the DynmapServer much more abstract, in particular, I removed the need for any files. I then implemented two DynmapServers, one that is local (and uses files, as before) and one that uses HTTP to access other dynmap servers.
One missing point at the moment is caching, but that can easily be implemented (I didn't really need it as everything runs on a single physical server.)
Feedback is welcome! :)
Edit: To use it, simply enter the URL of a dynmap server as Url: http://... into the config file, instead of Folder. The JsonFileClientUpdateComponent needs to be enabled for this dynmap, just as if it would be a local one.
I know that these changes are pretty big, but I thought that they'd be worth sharing. We have multiple dynmaps distributed across multiple virtual servers on the same machine. Currently, Dynmap-Multiserver doesn't support multiple servers, only multiple dynmaps on the same server.
I refactored some stuff and made the DynmapServer much more abstract, in particular, I removed the need for any files. I then implemented two DynmapServers, one that is local (and uses files, as before) and one that uses HTTP to access other dynmap servers. One missing point at the moment is caching, but that can easily be implemented (I didn't really need it as everything runs on a single physical server.)
Feedback is welcome! :)
Edit: To use it, simply enter the URL of a dynmap server as
Url: http://...into the config file, instead ofFolder. TheJsonFileClientUpdateComponentneeds to be enabled for this dynmap, just as if it would be a local one.