----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: https://reviews.apache.org/r/28263/#review62394 -----------------------------------------------------------
Is there a use-case for debug.json? This was exposed as debug.json _so that_ people do not rely on this, we wanted it for instrospection purposes only (we were having issues). The purpose of Files was to hide the underlying file system from users of the API. I'm curious, is browse.json insufficient? Would we want to expose all the "virtual paths" when one hits browse.json without an argument? e.g. $ curl .../browse.json /log /containers/foo/ /containers/bar/ ... - Ben Mahler On Nov. 19, 2014, 11:48 p.m., Cody Maloney wrote: > > ----------------------------------------------------------- > This is an automatically generated e-mail. To reply, visit: > https://reviews.apache.org/r/28263/ > ----------------------------------------------------------- > > (Updated Nov. 19, 2014, 11:48 p.m.) > > > Review request for mesos and Dominic Hamon. > > > Repository: mesos-git > > > Description > ------- > > See summary > > > Diffs > ----- > > src/files/files.cpp 12e8f75aa7bd77d2e81d5d3a7a4d09dd915854aa > > Diff: https://reviews.apache.org/r/28263/diff/ > > > Testing > ------- > > make distcheck ubuntu 14.04 > > > Thanks, > > Cody Maloney > >
