[
https://issues.apache.org/jira/browse/MESOS-1224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13984673#comment-13984673
]
Timothy St. Clair edited comment on MESOS-1224 at 4/29/14 7:54 PM:
-------------------------------------------------------------------
So I took a look.
Couple of quick notes: I wouldn't interject specific symbol + lookup in the
general purpose library - stout as it has implied semantics.
I'll try to push some examples to my testing repo.
was (Author: tstclair):
I'll take a look shortly, FWIW wrapping w/shared_ptr on returns is usually good
form given that it will live in stout.
Also the base class will need a couple of basic signatures for version checking
+ potential dynamic_casts.
> Add dynamic loadable library abstraction to stout.
> --------------------------------------------------
>
> Key: MESOS-1224
> URL: https://issues.apache.org/jira/browse/MESOS-1224
> Project: Mesos
> Issue Type: Improvement
> Components: stout
> Reporter: Niklas Quarfot Nielsen
> Assignee: Niklas Quarfot Nielsen
> Priority: Minor
> Labels: extensibility
> Fix For: 0.19.0
>
>
> Adding a first class primitive, abstraction and process for dynamic library
> writing and loading can make it easier to extend inner workings of Mesos.
> Making it possible to have dynamic loadable resource allocators, isolators,
> containerizes, authenticators and much more.
> I think this could be a powerful feature, as we get even more extensible and
> flexible ways of setting up Mesos - but also for isolating dependencies and
> complexity in external libraries and to ease experimentation with new
> features. For example, imagine a loadable allocators which contains a VM
> (Lua, Python, ...) which makes it possible to try out new allocator
> algorithms without forcing those dependencies into the project.
> BenH and I chatted about the concrete details and I will follow up with small
> write-up/proposal.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
