I guess I got a little carried away there. I'm not suggesting that XML should replace your existing database format. However, having code to export that data to XML does make it much more accessible, especially in the long term.
I'm not 100% sure about performance issues, but I think you'll find that you get better performance from going to XML and then to the various other formats via a fast XSL parser than going directly from your current format to each of the target formats.
Patrick
> -----Original Message----- > From: stas [mailto:stas@newdel.net] > Sent: Tuesday, May 08, 2001 9:25 AM > To: Fusebox > Subject: Re: XSLT with Fusebox and JSP and whatever else > > > But do you keep track of all these XML files? What about > performance issues > when these files grow too large? I mean, we are talking about flat files > here, no? > > ----- Original Message ----- > From: "Patrick McElhaney" <pmcelhaney@bizjournals.com> > > Additionally, it makes sense just to have your data in XML so that > it doesn't become legacyware. Because it's just a text file, you can > put it anywhere. You can work with it programmatically through an API. > You can open it up in a web browser or an XML editor or a regular > old text editor. You can transform it just about any format very > easily with XSL. You can embed it in other XML documents (or vice > versa). And when the technology catches up to the standards, > you'll be able to do all kinds of advanced searching and linking. > > Patrick > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Structure your ColdFusion code with Fusebox. Get the official book at http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/fusebox@houseoffusion.com/ Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
Fusebox
Patrick McElhaney