Federico Sacerdoti wrote:
Since Matt is going to be indisposed for a while due to his new baby, I
will take this one.
:O!!!
Dang, more people I need to send shirts to this month. :P
We are definately planning to implement this idea, and I'm glad you see
the need for it. Matt's idea, which
On a (very) slightly less pie-in-the-sky note...
Has anyone considered the utility of being able to select a subset of
cluster/host/metric data from the metadaemon? In other words, you
send a command that limits display to values that have been updated in
the last 60 seconds, or a particular
It's also worth noting that there's no particular reason to avoid
developing other front-ends to Ganglia. If you'd rather build one your way
using a particular technology or library that better suits your needs, the
existing architecture makes it pretty easy for you to do so. Almost as if
it
Well there are a few reasons. I know only a cursory bit about xslt,
however, so let me know if I'm off base on any of these.
We chose PHP over XSLT because:
-PHP is faster, and more mature.
-Can handle CGI variables which keep state between different HTML views.
-Can read form data given by user
The Ganglia web frontend uses PHP to transform xml to html (I think). Why
was that method chosen instead of using PHP to make calls to xslt scripts to
do the transformation? Is there a belief that PHP is better than xsl for
coding xml to html transformations? Does the Ganglia web front end include
