Mailing-List: contact dev-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
MIME-Version: 1.0
In-Reply-To: <C12FC79D-B10E-4085-86F2-6202355F96F9@gmail.com>
References: <CAC2gziuM9HuQ9PgH3SbZt_gvQ66nPr1Ey3qsoBDY2fdnrJbc1w@mail.gmail.com>
 <C12FC79D-B10E-4085-86F2-6202355F96F9@gmail.com>
From: Wenzhao Zhang <wzhang27@ncsu.edu>
Date: Wed, 21 Jun 2017 09:02:04 -0400
Message-ID: <CAC2gzisNRHfVoJ=y+rqXn2uZ_tUUgeUJ=27NmGP-uz92jrOPOA@mail.gmail.com>
Subject: Re: An independent server communicating between master and client
To: dev@mesos.apache.org
Content-Type: multipart/alternative; boundary="94eb2c0ef362ba16d6055277fa20"
archived-at: Wed, 21 Jun 2017 13:02:32 -0000

--94eb2c0ef362ba16d6055277fa20
Content-Type: text/plain; charset="UTF-8"

Thanks,
But I think Mesos right now uses Proto2, not Proto3.
If I switch entirely to a REST server with ProtocalBuffer, I think this
will be fully compatible with Mesos?

Thanks
Wenzhao


On Wed, Jun 21, 2017 at 3:53 AM, James Peach <jorgar@gmail.com> wrote:

>
> > On Jun 20, 2017, at 11:23 AM, Wenzhao Zhang <wzhang27@ncsu.edu> wrote:
> >
> > Hello, All:
> >
> > I'm working on an independent server, which should be able to talk to the
> > master&client via  HTTP POST requests.
> > I setup a Jersey REST server.   My initial plan is to use *JSON/XML* to
> map
> > Entities, as this is widely used.
> >
> > However, I find some communication compatibility issues,
> > 1. I generate the Java classes from the *.proto files.
> >    I try to create an Event.Offers object via a REST (with *JSON*) call,
> > but get some data stream deserializing errors.
> >    I think this is because of the complex structure of the generated
> > classes. They are not POJO's, e.g. they don't have public constructors.
>
> Your JSON serializer needs to follow the Protobuf JSON mapping, with the
> exception that field names are not mapped to lowerCamelCase.
>
> https://developers.google.com/protocol-buffers/docs/proto3#json
>
>
> > 2. "src/cli/execute.cpp" sets "ContentType" to "*PROTOBUF*".
> >    I think in most cases, Mesos internally uses "PROTOBUF", not JSON.
> >
> > So, given the above issues,
> > Should I implement my server with *ProtocalBuffer*, is this a better
> > approach?
> > Or should I try to convert PROTOBUF to JSON inside Mesos?
> >
> > Could anyone kindly give some suggestions? I become confused on this
> point.
> >
> > Thanks very much
> > Wenzhao
>
>

--94eb2c0ef362ba16d6055277fa20--