hobbitdxboard - Should xboard honor the fields= definition ?
All,
I am playing with hobbitdboard & hobbitdxboard. Should the hobbitdxboard honor the fields= definition like hobbitdboard does ? In my testing I have found that it does not. Most desireable would be to choose to have the full log msg listed.
thank you, ~Steve
Looking at hobbitd/hobbitd.c it appears that the hobbitdxboard response fields are hardcoded. Though my C code reading ability is non-existent. And in thinking about it, querying hobbit for the a complete xboard w/ the full log msg could be very, very intensive.
~Steve
On Friday 13 April 2007 09:48, s_aiello at comcast.net wrote:
All,
I am playing with hobbitdboard & hobbitdxboard. Should the hobbitdxboard honor the fields= definition like hobbitdboard does ? In my testing I have found that it does not. Most desireable would be to choose to have the full log msg listed.
thank you, ~Steve
On Fri, Apr 13, 2007 at 09:48:35AM -0400, s_aiello at comcast.net wrote:
I am playing with hobbitdboard & hobbitdxboard. Should the hobbitdxboard honor the fields= definition like hobbitdboard does ?
It doesn't.
I don't know if it's OK in XML to leave out certain attributes - I suppose it is, and in that case there shouldn't be a problem with implementing the "fields" option to hobbitdxboard.
In my testing I have found that it does not. Most desireable would be to choose to have the full log msg listed.
The <MessageSummary> attribute has the first line of the status message, which is usually a summary of the data. The amount XML data generated by hobbitdxboard is already rather large - I'd rather not increase that much more.
Regards, Henrik
On Tuesday 17 April 2007 11:23, Henrik Stoerner wrote:
On Fri, Apr 13, 2007 at 09:48:35AM -0400, s_aiello at comcast.net wrote:
I am playing with hobbitdboard & hobbitdxboard. Should the hobbitdxboard honor the fields= definition like hobbitdboard does ?
It doesn't.
I don't know if it's OK in XML to leave out certain attributes - I suppose it is, and in that case there shouldn't be a problem with implementing the "fields" option to hobbitdxboard.
In my testing I have found that it does not. Most desireable would be to choose to have the full log msg listed.
The <MessageSummary> attribute has the first line of the status message, which is usually a summary of the data. The amount XML data generated by hobbitdxboard is already rather large - I'd rather not increase that much more.
Thinking back on the sheer amount of data now, I have to agree with you. Initially I was asking since I am being asked about the capability of other in-house webapp tools pulling data out of Hobbit. I think the data provided already in the XML feed is plenty. If those other tools want to provide the Log msg, well the can just have a hyperlink to the hobbit report via hobbit-cgi/bb-hostsvc.sh.
Other tools really don't even have this option, i.e. Quest's FogLight. So I really have to thank you that it is so easy in Hobbit.
Thank you for your response, ~Steve
s_aiello at comcast.net wrote:
Thinking back on the sheer amount of data now, I have to agree with you. Initially I was asking since I am being asked about the capability of other in-house webapp tools pulling data out of Hobbit. I think the data provided already in the XML feed is plenty. If those other tools want to provide the Log msg, well the can just have a hyperlink to the hobbit report via hobbit-cgi/bb-hostsvc.sh.
Other tools really don't even have this option, i.e. Quest's FogLight. So I really have to thank you that it is so easy in Hobbit.
Thank you for your response, ~Steve
I was asked about getting hobbit data as xml last year and that's exactly what we did. We provide the xml and they have a web app that provides a link back to the hobbit page if they want to see more detail.
John
participants (3)
-
henrik＠hswn.dk
-
johng＠idttechnology.com
-
s_aiello＠comcast.net