How difficult is it to replace the RapidXML XML parser with another parser, such as pugiXML? Is this a change-case that has been planned and streamlined, and therefore a straight-forward effort, or is it a lengthy and detailed affair that requires intimate knowledge of PropertyTree internal workings? I ask because my organization predicts we likely will change back-and-forth between competing implementations (RapdidXML, Kranf xmlParser, pugiXML) as time goes by, which implies that we should have some kind of wrapper around the XML parser. I am investigating how well boost's "property tree" could server as that wrapper. And, in fact, we currently want pugiXML because of it's wide-char supporthttp://code.google.com/p/pugixml/source/browse/#svn/branches/unicode, and because it has XPath support (granted PropertyTree assuredly won't "wrap" the XPath capability, but we'll deal with that separately). Brent Arias Software Architect Lumension Security(tm) Tel ~ (480) 444-1607 Fax ~ (480) 970-6323 brent.arias@lumension.commailto:brent.arias@lumension.com