Steven Niemitz

Much better volume support is coming soon! It sounds like for your use case you want to use the docker volume support built into mesos, thats next on my list...

Thanks for the PR! Some thoughts I have after trying to get the quickstart script working: * Should we fail fast if minimesosFile is missing in the root directory? **...

+1 also, this is a great idea!

short answer: `--volume` is pretty much useless. long answer: I've been experimenting with much better volume support. I think this would be a killer feature and a huge win, however...

So, if I understand what you're asking, there is currently no way to do it. There's no support in the scheduler to advertise one port (for resource downloading for example)...

Can you comment on what this is trying to fix/improve?

Cool, seems good to me. Have you tested the backwards-compat case with an old client -> new server (and vis versa)?

I've been running a custom build that replaced `SleepingWaitStrategy` with `BlockingWaitStrategy`, which completely removes the CPU overhead of the disruptor thread. However is does add a very slight overhead to...

I do like the idea of being able to configure this more easily. It seems like the SleepingWaitStrategy does have some kinks in it that could be worked out though...

We recently just landed something like this in [bazel-bsp](https://github.com/JetBrains/bazel-bsp), it can export a set of bloop projects given a set of bazel targets. Not exactly the same thing but similar?