On Wed, Nov 30, 2016 at 1:41 PM, Jim Jagielski <[email protected]> wrote:
> > On Nov 30, 2016, at 2:31 PM, William A Rowe Jr <[email protected]> > wrote: > > > > On Wed, Nov 30, 2016 at 1:27 PM, Jim Jagielski <[email protected]> wrote: > > > > > On Nov 30, 2016, at 1:56 PM, William A Rowe Jr <[email protected]> > wrote: > > > > > > > > > There's no way to anticipate the "right way" to map json > > > tables to presentation-level results. > > > > ??? > > > > Certainly that is the job of the xlate provider that > > would be used, wouldn't it. Or are you suggesting that > > JSON itself isn't suitable as a data format in this case? > > > > I'm asking how one would maintain the xslt for the half dozen > > json data providers of mod_status extensions within the stock > > distro, PLUS any mod_status extension providers in the third > > party world of modules? > > > > Ummmm.... the data providers that hook into mod_status simply > push JSON. Same w/ any other extension providers. That is, > ALL mod_status does is provide JSON data; mod_status_html takes > that JSON format and xlates it to HTML; mod_status_plain takes > it and xlates it to simple text. > > Where does JSON fail and bean succeed? > > Other than being something that I brought up, I'm not sure > I understand your resistance, or why/how BMX is "better" > than JSON. BMX is entireliy JSON. I have no argument with your suggestion, which is why I'm bringing it up (you are the only one on the private list to have pushed back against adopting mod_bmx, why so I'm really not clear.) As you can see in the sources, mod_bmx_status is interrogating the scoreboard, not mod_status, for the underlying data. Beans provide a completely extensible way to map additional data for mod_bmx to present. What I'm questioning is whether a transliteration of unknown-future data can ever succeed, or whether third party modules won't need both a presentation-layer and json/bean-layer to represent their data in user and machine usable formats. I'm not familiar with a good interface for json -> html, pointers would be appreciated. I'm fairly familiar with xml -> json + xml -> html using xslt. That's presuming you know the entire plane of data to represent.
