At 12:41 -0800 on 2/1/06, Jordan K. Hubbard wrote:
In Tiger, the primary goal was to provide the APIs and evangelize
them at WWDC. In >Leopard, we'll be using them in a lot more
darwin projects. Unfortunately, that doesn't give >you a lot of
examples to work from right now. Fortunately, the asl(3) man page
is very >good and provides code examples, so this isn't a big
deal. You can also use syslog(1) to >query the results and
simulate logging from various types of applications.
If you wouldn't mind, and with the goal of evangelization, could
you briefly explain what the advantages of asl over syslog are?
"Briefly" speaking, it allows for an open-ended set of log message
attributes (unlike the fixed set of facilities in syslog(3)), it
unifies the character encoding of all log messages (so messages
aren't in an arbitrarily mixed set of encodings), it eliminates the
profusion of individual log files in favor of a single log database,
it provides an advanced search and filter API, it allows application
logging behavior to be controlled remotely, and it's got a much more
flexible plug-in model for handling messages in a variety of ways.
It's hard to encapsulate everything that took about half an hour (and
with the benefit of slides) to describe at the last WWDC, however, so
those with ADC memberships are encouraged to view the on-line
presentation video (session #510, "Core OS Enhancements for BSD
Developers") and/or download the session slides. I'm not trying to
cop out on evangelizing ASL here, it's simply far more efficient for
me to leverage resources that already exist for this (see also http://
developer.apple.com/samplecode/SampleD/SampleD.html).
- Jordan
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Darwin-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/darwin-dev/email@hidden
