Hi John, If you're using Java there is already a prototype client atop the new Scheduler HTTP API using RxJava: https://github.com/mesosphere/mesos-rxjava Happy to provide more info if interested.
--Ben Whitehead On Thu, Dec 3, 2015 at 11:52 AM, John Omernik <[email protected]> wrote: > Thank you! > > On Thu, Dec 3, 2015 at 1:40 PM, Vinod Kone <[email protected]> wrote: > >> Yes, that's the plan. >> >> Here are the related epics tracking the work: MESOS-2288 >> <https://issues.apache.org/jira/browse/MESOS-2288> and MESOS-3302 >> <https://issues.apache.org/jira/browse/MESOS-3302> >> >> The user doc for the scheduler API is >> https://github.com/apache/mesos/blob/master/docs/scheduler-http-api.md >> >> On Thu, Dec 3, 2015 at 11:34 AM, John Omernik <[email protected]> wrote: >> >>> Somewhere in the back of my brain I thought I read something about a >>> migration away from using the mesos native lib and going to a more generic >>> API approach to support better portability and less reliance on the lib. >>> >>> I read about this before I understood things well (or as well I do now I >>> should say). Am I misremembering reading about this? I can't find any >>> stories/documentation on this. If I am correct on this, can someone point >>> me to a JIRA or a discussion on how this is supposed to work? I.e. is the >>> goal to migrate all frameworks off the native library to deprecate it etc? >>> >>> Thanks, sorry for the weird questions. >>> >>> John >>> >> >> >
