> On Oct. 19, 2015, 3:34 p.m., Anand Mazumdar wrote: > > docs/scheduler-http-api.md, line 59 > > <https://reviews.apache.org/r/39452/diff/2/?file=1101221#file1101221line59> > > > > Should we also mention why just encoding one event per chunk won't > > suffice and why we needed this ? > > > > How about: > > > > ```Network intermediataries e.g. proxies are free to change the chunk > > boundaries and this should not have any effect on the recipient > > application(scheduler layer). We wanted a way to delimit/encode two events > > for JSON/Protobuf responses consistently and RecordIO format allowed us to > > do that.```
+1 - Ben ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/39452/#review103172 ----------------------------------------------------------- On Oct. 20, 2015, 2:30 p.m., Marco Massenzio wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/39452/ > ----------------------------------------------------------- > > (Updated Oct. 20, 2015, 2:30 p.m.) > > > Review request for mesos, Anand Mazumdar and Vinod Kone. > > > Bugs: MESOS-3566 > https://issues.apache.org/jira/browse/MESOS-3566 > > > Repository: mesos > > > Description > ------- > > Added the description of the RecordIO format to the HTTP API > document with example code (Python) to decode. > > > Diffs > ----- > > docs/scheduler-http-api.md de6cfc9e009a857ca45291b2dadce2a3b8199787 > > Diff: https://reviews.apache.org/r/39452/diff/ > > > Testing > ------- > > > Thanks, > > Marco Massenzio > >
