"Headless" studio plugin

[LucySweetWork]

It would be useful if the rojo studio plugin could support interaction by other studio plugins rather than just by the UI.
For example, I could have another plugin tell rojo to sync from a specific server at a specific port and rojo would do that. It would be even better if rojo could then tell my original plugin "hey, I've successfully synced the content from that server" so I could get feedback on whether the sync worked or not.
This would be useful to weave rojo into custom integrations we use.

[boatbomber]

I'd love to flesh this out a bit more. What use cases would we be serving with this headless Studio plugin? Specifically, what use cases would this plugin-sided API fill that wouldn't be filled by server-sided API (#55 & #497)?

[Boegie19]

@boatbomber
I mind be wrong but does the server-sided API not only allow 1 connection

Also in the long term I think splitting off the web server and client from rojo project would work out better
since it will allow others to use that to create there own roblox plugins that need to communicate to and from roblox studio to the pc

1 this would allow other projects to use the same bridge only different endpoints maybe on the same port
2 this would allow other applications and roblox plugins to communicate to rojo trough the web api
3 the headless roblox plugin would allow other plugins to communicate to the webserver to what ever endpoint they want so it and have there own programs react on that endpoint

Still this could create some problems aka end point name clashes or malicious roblox plugins or programs abusing the api delete stuff