> Any other reason to use XML if you're not referring to
> importing/exporting syndicated content
> with another site, another server?

I use XML so extensively at this point that answering this question is kinda
difficult... kinda like, "Any other reasons to own a car beyond driving to
work?" :D

- Supplying content to client applications... Newzcrawler lets me know when
my blog detects a new, incoming link by checking my CF-generated
referrers.xml file.

- Remote Procedure Calls... I can post to my blog via a third-party
application using XML-RPC.

- On a related note, I use a standardized XML file to tell those third-party
applications what APIs that I support.

- Storing content... JournURL keeps the actual text of a user's entries in a
WDDX packet, with the database serving as a SQL-friendly index.

- Storing non-essential metadata... since I've already got that WDDX packet
sitting there, I can stick any old data in it. No need to add tables or
columns to the database, unless the new data is important stuff that needs
to be indexed.

- When I want to tell an author that I've linked to her, I automatically
send an XML "ping" to her server. Similarly, other folks can send me XML
notifications which will magically appear as annotations on my blog.

- Configuration files... I find simple XML easier to edit than .INI-style
stuff.

--
Roger Benningfield
JournURL
community-powered weblogs & diaries
work: http://journurl.com/
blog: http://admin.support.journurl.com/


~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4
Subscription: 
http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq

Your ad could be here. Monies from ads go to support these lists and provide more 
resources for the community. 
http://www.fusionauthority.com/ads.cfm

                                Unsubscribe: 
http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
                                

Reply via email to