> On Feb. 24, 2016, 7:57 a.m., Adam B wrote: > > docs/app-framework-development-guide.md, lines 137-139 > > <https://reviews.apache.org/r/43819/diff/1/?file=1263766#file1263766line137> > > > > Let's be very explicit that they'll need to instantiate a > > MesosSchedulerDriver and call these methods on it. Probably also want to > > document the MesosSchedulerDriver constructors so they know how to > > instantiate one.
Refered to the test_framework.cpp instead for proper use of the the schedulerDriver... - Joerg ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/43819/#review120465 ----------------------------------------------------------- On March 7, 2016, 8:05 p.m., Joerg Schad wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/43819/ > ----------------------------------------------------------- > > (Updated March 7, 2016, 8:05 p.m.) > > > Review request for mesos, Adam B and Neil Conway. > > > Repository: mesos > > > Description > ------- > > Previously the app-framework-development-guide only explained the scheduler > callback interface. Equally important when developing frameworks is the > knowledge if potential actions a scheduler can trigger via the > SchedulerDriver. > > > Diffs > ----- > > docs/app-framework-development-guide.md > 55f09c7cf2262dda98dcc8b63b1e36ab78296141 > > Diff: https://reviews.apache.org/r/43819/diff/ > > > Testing > ------- > > Viewed via gist (https://gist.github.com/joerg84/b4bf279a55e1b62051e6) and > via docker website container. > > > Thanks, > > Joerg Schad > >
