FastXmlPull parser is not threadsafe, through use of global Regexp objects

Note further with reference to comment on FLUID-3224 - the fastXmlPull parser as it stands is not threadsafe - the RegExp objects that it uses have a static lifetime and will become corrupt on concurrent access. This is a critical issue wrt. Fluid Engage since with the renderer being deployed on the serverside, if more than one thread attempts to load a template concurrently, the resulting structure will become corrupt.

Since original filing, this issue has been found to be related to a critical issue on the client-side. As a result of not adhering to Fluid standards for namespacing and versioning, this module will cause a failure in a page where it is included multiply, through lack of proper registration of the members of the "XMLP" structure and its priority has been increased.