Re: AW: [PHP] What's your call on XML?

You obviously don't read the archives much, because others have posted about this, as have I, but I'll reply again. Most people aren't advocating storing data in XML files to be queried against (although there are some tools to do it, it's too new, and SQL is too entrenched). Store data in a storage tool (sql server in this case). Transfer data in a markup language that gives metainfo about the data (XML). The examples given before (isyndicate) - yes, they could just give a database dump. What happens when they want to include extra info? They're giving author, date, title, etc. What if they wanted to add an extra field - 'expiration date' for example? Adding one extra field to your 'text dump' throws everyone's hand written parsers for a loop, and everything breaks. Exchanging data with a few select partners by hand is fine, but adhering to some type of exchange standard (XML in this case) makes FAR more sense for dynamic data payloads. There are other benefits to XML that can't be had easily, over the long term, with doing things 'by hand'. Hope that makes sense... Sebastian Stadtlich wrote: > Forget about XML... it sucks... > right now i can't imagine one Projekt on this earth that would need XML. > don't ever think about replacing your database with XML-Files. > one thing that XML clains to be perfect in is in exchanging data files... > what's wrong with a SQL-Dump or a textfile which structure you know? ( > basically > that is what XML is all about).. > Sebastian > p.s: if i'm wrong please someone point me to a projekt that was done in XML > and could > not be done significantly faster with a Database...... ========================== Michael Kimsal PHP Meta search http://www.phphelpdesk.com/search/ PHP Training courses http://www.tapinternet.com/php/