Linked by Eugenia Loli on Thu 6th Oct 2005 19:14 UTC
Windows Recently, several representatives from Windows IT Pro Magazine received a briefing about the Beta 1 version of Longhorn Server, the next member of the Windows Server family, currently due in the first quarter of 2007, or about six months after Windows Vista ships in late 2006.
Thread beginning with comment 41234
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Innovation
by Clinton on Thu 6th Oct 2005 22:19 UTC in reply to "Innovation"
Clinton
Member since:
2005-07-05

It seems to me that XML is probably, bar none, the dumbest format for log files. XML is great for certain types of data, but I don't think log file data is one of them.

Reply Parent Score: 1

RE[2]: Innovation
by jayson.knight on Fri 7th Oct 2005 00:37 in reply to "RE: Innovation"
jayson.knight Member since:
2005-07-06

So what would be a better format? XML is a great choice for this as writing front end applications for parsing them will be a snap given the parsing infrastructure is already here.

Reply Parent Score: 1

RE[2]: Innovation
by butters on Fri 7th Oct 2005 01:13 in reply to "RE: Innovation"
butters Member since:
2005-07-08

"It seems to me that XML is probably, bar none, the dumbest format for log files. XML is great for certain types of data, but I don't think log file data is one of them."

Yeah, I'm going to go ahead and disagree with you there. It is the best possible choice? Maybe not. It largely depends on whether reading the raw log is important to you, or if you're more concerned with having rich GUI tools and APIs for doing thins with the data.

If I were Microsoft, I would immediately choose this application as a perfect poster child for the effectiveness of the .NET framework. Make each "entry" a object implementing a LogEvent class, with loads of nice information on the event, where it came from, lists of subscribers, and other stuff. Then make nice GUI apps that and APIs that leverage this class. I guess they have a mighty aversion to their own framework, because this seems like a good place to use it.

But in any case, XML isn't a bad option. There are tons of efficient XML code generators and parsers already written, it's an "open standard," and it allows for a good deal of richness. And if XML is without a doubt the worst format than this is better?:

Oct 6 15:55:17 disarray e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Oct 6 16:00:01 disarray cron[28633]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Oct 6 16:00:01 disarray cron[28634]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Oct 6 16:10:01 disarray cron[28646]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Oct 6 16:12:57 disarray e100: eth0: e100_watchdog: link down
Oct 6 16:12:59 disarray e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex
Oct 6 16:14:18 disarray su(pam_unix)[9425]: session closed for user root
Oct 6 16:20:01 disarray cron[28723]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Oct 6 16:29:19 disarray e100: eth0: e100_watchdog: link down
Oct 6 16:29:21 disarray e100: eth0: e100_watchdog: link up, 100Mbps, full-duplex

Reply Parent Score: 1