On 10/28/05, Joseph Flanigan <[EMAIL PROTECTED]> wrote: > This is my opinion. The reason is that XML is primarily an exchange > language.
You do know how horrendously commong XML configuration files are in just about everything these days (not just web application frameworks), right? Are you saying everyone who does this is misguided? > 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. But it isn't used as a data store in Mach-II, at least not the way I think of a data store. It's a controller file, pure and simple. > A web application can have 1000s of events, as such, a management > system is a better choice to store events. It occurred to me that > Mach's XML was a excuse to demonstrate CF's ability to handle XML > and not a real serious event store. Um, after this initial thought occurred to you, did you look into it or think on it any further, or did you just say "Yep, that's it! They're just showing off XML handling!" and call it a day? XML is used for this sort of thing in many, MANY instances throughout the computing world because it's extremely well-suited for this purpose. Unless everyone who's ever done things this way is just wrong and didn't know about these "databases" of which you speak. -- Matt Woodward [EMAIL PROTECTED] http://www.mattwoodward.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]
