On 1/27/12 7:43 AM, Alex Dean wrote: > 1. As a user, I sometimes want to consume ganglia data in other > contexts (not just in gweb). I'd much prefer working with JSON > instead of XML.
I think that most developers would prefer json to xml, if for no other reason than json libraries/modules are available for all major languages AND they are much much much simpler to write against. > 2. gweb currently allows users to download metrics as > JSON. This is done by getting XML from gmetad, and transforming it > into JSON in PHP. If gmetad could create JSON natively, gweb code > could probably be streamlined. I agree! Using PHP to read XML and output json is a ridiculous inefficiency on a few levels. It means that people who want json have to run an entire webserver stack to generate the json, consumers must request the json via http instead of writing simple direct socket operations, the results of the fetch are proxied through whatever caching mechanisms which may be present in the webserver/php config and therefore may not come with any gurantee of freshness, the ultimate source of the data ends up being rrd files on disk which means even a single "what is the current value of metric X" could be a very slow operation instead of the quick memory based hash lookup that would be available if the json came from lower in the stack.... -Dave ------------------------------------------------------------------------------ Try before you buy = See our experts in action! The most comprehensive online learning library for Microsoft developers is just $99.99! Visual Studio, SharePoint, SQL - plus HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when you subscribe now! http://p.sf.net/sfu/learndevnow-dev2 _______________________________________________ Ganglia-developers mailing list Ganglia-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/ganglia-developers
