TBH I'm not particularly happy about closing this as Won't Fix.
It's unexpected behavior and potentially a "security" issue. If you want to have it disabled at a given time, you have to restart, which is probably not the time that you want to restart.
It shouldn't be too complicated. My branch is probably outdated by now, but tbh you didn't followup one the issues you had with it. If we are able to shutdown the remote properly on OpenLP shutdown (which we should!!), then we have to be able to do that without a OpenLP shutdown. Otherwise something is wrong about the architecture. Also note that other plugins can be disabled/enabled that way.
The behavior is no longer valid. The API is running all the time in version 3 so this is not a valid defect anymore.
The remote plugin is only a placeholder for web code and not the web server.
So once downloaded it's always there, always running? In that case I'd open a new bug to enable/disable the API. My remarks would pretty much remain unchanged...
TBH I'm not particularly happy about closing this as Won't Fix.
It's unexpected behavior and potentially a "security" issue. If you want to have it disabled at a given time, you have to restart, which is probably not the time that you want to restart.
It shouldn't be too complicated. My branch is probably outdated by now, but tbh you didn't followup one the issues you had with it. If we are able to shutdown the remote properly on OpenLP shutdown (which we should!!), then we have to be able to do that without a OpenLP shutdown. Otherwise something is wrong about the architecture. Also note that other plugins can be disabled/enabled that way.