[ https://issues.apache.org/jira/browse/MESOS-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14077843#comment-14077843 ]
Niklas Quarfot Nielsen commented on MESOS-1384: ----------------------------------------------- In my proof-of-concept, the DynamicLibrary need to be provided when calling ::create() (which is called ::init() there - [~bernd-mesos] suggested ::load() instead, which I like better). I was suggesting that we could have a ::load()/::create() have an overloaded version that creates the DynamicLibrary and ties it to the lifespan of the module object. Should we aim for both, only the first or the latter? :-) > 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 > Assignee: Niklas Quarfot Nielsen > > 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)