Hi,
First, I should try to better read more documentation. Thanks for the info.
Many applications manage alarms. An alarm service even seems like a
natural archetype. Relying on a rich and fascinating infrastructure
today (ex: XSLT, XML, J2EE, Web), "messy things" can now be better
abstracted and managed (programmed) functionally, and with quite a bit
of possibilities, I find.
Thank you.
Cheers,
ac
Yes, indeed. I think XSLT works best in a very closed functional world where
the output is a simple function of the input. Messy things like telling
security admins what has gone wrong are best handled in a different layer.
Michael Kay
http://www.saxonica.com/
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--