> The reason is that XML is primarily an exchange > language. Because it is based on an abstract syntax notation, DTD, it > is very easy to overload and mis-use as a data store such as in Mach.
Yes, it stared as an exchange language, but the ability to build structured, checked documents lends itself well to other applications - this isn't a misuse. A "butter" knife does a good job spreading jam; does that make it a misuse? I think others agree: Fusebox, Mach-II, Model-Glue, Struts, Spring, ASP.NET, Coldspring, J2EE, heck, even Cisco routers now use XML for configuration. > A web application can have 1000s of events, as such, a management > system is a better choice to store events. An application-level event management system of any use needs to be able to show these events in a structured format where application flow can be "seen". XML provides a very nice structure for this. -Joe -- Get Glued! The Model-Glue ColdFusion Framework http://www.model-glue.com ---------------------------------------------------------- You are subscribed to cfcdev. To unsubscribe, send an email to [email protected] with the words 'unsubscribe cfcdev' as the subject of the email. CFCDev is run by CFCZone (www.cfczone.org) and supported by CFXHosting (www.cfxhosting.com). CFCDev is supported by New Atlanta, makers of BlueDragon http://www.newatlanta.com/products/bluedragon/index.cfm An archive of the CFCDev list is available at www.mail-archive.com/[email protected]
