Another newbie question:
I am just trying to figure out how this whole xml thing works - I keep
seeing examples of serializing in WDDX in which the sample code creates
a text file like:
<?xml version="1.0" ?>
<contact_information>
<person>
<last_name>Blum</last_name>
<first_name>Jason</first_name>
</person>
<person>
<last_name>Costanza</last_name>
<first_name>Goerge</first_name>
</person>
</contact_information>
and then serializes it... and then takes output and deserializes it back
into a structure.
At what point does this involve "parsing" Isn't WDDX just recognizing
the beginning and end tags and forming a structure out of them dumbly
without being aware of what those tags mean? That's all I'm after
because then I can loop through the structure and output it different
ways...
I guess I understood the whole point of XML to be to allow the client to
do that "outputting in different ways" but since I can't assume the
client is the latest version of IE, I figured I should do it for them by
hitting the server.
When I hear talk of installing a parser in ColdFusion, my head spins,
particularly because all I want to do is access this xml file like a
datasource and I know I could just write a custom tag to create a
structure out of the fields...
That said, I know I am "missing the point" so I figured who better to
ask then the cf community!
Thanks for your help!
-Jason
______________________________________________________________________
Get the mailserver that powers this list at http://www.coolfusion.com
FAQ: http://www.thenetprofits.co.uk/coldfusion/faq
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
