Allow plugins to expose their API (optionally over RPC as well) #292

Open
Zapotek opened this Issue Oct 3, 2012 · 3 comments

Comments

Projects
None yet
1 participant
@Zapotek
Owner

Zapotek commented Oct 3, 2012

There's no reason why plugins shouldn't be able to be controlled programmatically via their API.

After all, plugins are there to extend the framework's functionality; no sense treating them as dumb fire-and-forget components and not allowing them the option to expose their API, even over RPC if they so choose.

@ghost ghost assigned Zapotek Oct 3, 2012

@Zapotek

This comment has been minimized.

Show comment Hide comment
@Zapotek

Zapotek Dec 6, 2012

Owner

Pushing this to v0.5 since plugins will have to be updated to work asynchronously.

Owner

Zapotek commented Dec 6, 2012

Pushing this to v0.5 since plugins will have to be updated to work asynchronously.

@Zapotek

This comment has been minimized.

Show comment Hide comment
@Zapotek

Zapotek Apr 24, 2014

Owner

Reviewing this again, plugins don't actually need to be rewritten to work asynchronously in order for this to work. The existing threaded model of all plugins running in parallel would still work fine and async callbacks can be added for newer plugins if need be.

In addition, the Dispatcher's RPCD Handler code (that exposes RPC APIs for modular components dynamically) can be leveraged for this purpose too.

This needs much less work than originally estimated, yay.

Owner

Zapotek commented Apr 24, 2014

Reviewing this again, plugins don't actually need to be rewritten to work asynchronously in order for this to work. The existing threaded model of all plugins running in parallel would still work fine and async callbacks can be added for newer plugins if need be.

In addition, the Dispatcher's RPCD Handler code (that exposes RPC APIs for modular components dynamically) can be leveraged for this purpose too.

This needs much less work than originally estimated, yay.

@Zapotek

This comment has been minimized.

Show comment Hide comment
@Zapotek

Zapotek May 24, 2014

Owner

Removing from the v0.5 milestone, it's a nice feature but not necessary, at least not yet.

Owner

Zapotek commented May 24, 2014

Removing from the v0.5 milestone, it's a nice feature but not necessary, at least not yet.

@Zapotek Zapotek removed this from the v0.5 milestone May 24, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment