|
|
|
|
|
by nteon
4307 days ago
|
|
I'm not sure I see the benefit of plugin discovery or separate namespaces. Loading a plugin gives you a Plugin struct, which is a namespace to lookup symbols (functions + globals) from that plugin. Most plugins would I think by necessity be application specific, so I'm not sure how much gain there in in some sort of plugin discovery. But the process of loading a plugin would also allow the plugin to call into your code to register handlers & data structures in the main application through init() functions. From a security perspective, executing arbitrary code in your address space in order to discover the contents of a plugin sounds ill-advised. To me, it looks like they're building the low level building blocks that allow a number of different higher level APIs to be built, which is pretty neat. |
|