On Thu, Dec 1, 2016 at 4:14 PM, Jim Jagielski <j...@jagunet.com> wrote:
> > > On Dec 1, 2016, at 2:16 PM, William A Rowe Jr <wr...@rowe-clan.net> > wrote: > > > > > > Note that mod_bmx_status entries focus on what most management > > frameworks are looking for, so thus far, it doesn't deliver an entire > > dataset per connection or worker thread. It certainly could, of course. > > Nor does it expose anything from any other beans created > by any other module. > > Can it? > > If so, exactly how. > > > > > Again, it simply iterates the entire contents of each bean presented > > to it's own print_bean_fn callback. If you have a look at; > > https://github.com/hyperic/mod_bmx/blob/master/modules/bmx/mod_bmx.h > > that should give you a somewhat higher altitude perspective on Aaron's > > API design. > > So mod_bmx_status has to query mod_bmx for "all beans" ?? > You are still thinking upside down. Think of mod_bmx as the data sink and mod_bmx_status as the data source. mod_bmx_status doesn't look at anything except the internals of httpd. Nobody queries mod_bmx_status directly except mod_bmx. The user agent queries mod_bmx.
