Sorry, I guess referring to it as the libmesos way of talking to the Mesos
master is a bit misleading.
And I stand corrected, the V0 is only an adaptor to the V1 interface which
still uses the undocumented RPC way of talking to the master (https://github.com/apache/mesos/blob/master/src/java/jni/org_apache_mesos_MesosSchedulerDriver.cpp
while using V1 versioned protobufs.
V1 one on the other hand talks to Mesos via a well defined HTTP API.
There's still a dependency on libmesos because the implementation of the
code that handles the HTTP requests is made available via JNI. The big
difference here being that someone else can implement their own Java only
version of the driver and the dependency on libmesos would be gone.
Apologies for the confusion.
On Thu, Jan 11, 2018 at 2:03 PM, Mohit Jaggi <[EMAIL PROTECTED]> wrote: