[
https://issues.apache.org/jira/browse/MESOS-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14002470#comment-14002470
]
Timothy St. Clair commented on MESOS-1384:
------------------------------------------
[~nnielsen] I like it, 2 minor comments:
1.) The MagicSymbol will likely need to reside where-ever the base is. Unless
you wanted different symbols for different base types for differentiation,
which is also useful.
2.) The name module::Module is a bit overloaded, perhaps mesos::Module unless
the code would live in someplace like stout?
> Add support for loadable MesosModule
> ------------------------------------
>
> Key: MESOS-1384
> URL: https://issues.apache.org/jira/browse/MESOS-1384
> Project: Mesos
> Issue Type: Improvement
> Affects Versions: 0.19.0
> Reporter: Timothy St. Clair
>
> I think we should break this into multiple phases.
> -(1) Let's get the dynamic library loading via a "stout-ified" version of
> https://github.com/timothysc/tests/blob/master/plugin_modules/DynamicLibrary.h.
> -
> *DONE*
> (2) Use (1) to instantiate some classes in Mesos (like an Authenticator
> and/or isolator) from a dynamic library. This will give us some more
> experience with how we want to name the underlying library symbol, how we
> want to specify flags for finding the library, what types of validation we
> want when loading a library.
> *TARGET*
> (3) After doing (2) for one or two classes in Mesos I think we can formalize
> the approach in a "mesos-ified" version of
> https://github.com/timothysc/tests/blob/master/plugin_modules/MesosModule.h.
> *NEXT*
--
This message was sent by Atlassian JIRA
(v6.2#6252)
