Question, and one I think I know the answer to: If I have a configuration XML file for an app, would it be better from a performance standpoint to keep the XML object around as my configuration object, or to pull out the data into a custom object structure (something simple, think object->array of objects)?
I would think that keeping the XML Object around would require more resources -- especially if using XPath. I'm not sure how much baggage I'm carrying around with an XML object. On the flip side, it's a built-in object, and if you use XPath once, you've got the classes loaded. And it doesn't get much easier than XPath + XML for data retrieval. My thinking says, dump XPath, load in the XML save it's data and dump it when done. Or dump XML all together and use a serialized object (PHP Serializer or some such). Opinions? _______________________________________________ [email protected] To change your subscription options or search the archive: http://chattyfig.figleaf.com/mailman/listinfo/flashcoders Brought to you by Fig Leaf Software Premier Authorized Adobe Consulting and Training http://www.figleaf.com http://training.figleaf.com
