[ https://issues.apache.org/jira/browse/MESOS-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14137499#comment-14137499 ]
Dominic Hamon commented on MESOS-1384: -------------------------------------- I'm missing some context here, I think. What problem is this trying to solve? The designs above seem to be reinventing some architecture and adding significant complexity that might already have a well-known solution elsewhere. If the goal is to split the monolithic mesos library into parts, then that's a build-time thing that can be done with well-defined public APIs between pieces. Is there more to it than that? > 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.3.4#6332)