Why does Superx++ advocate a special tier for XML in software architecture?
Superx++ advocates a special tier for XML in the architecture of distributed software systems because XML represents a special kind of data. XML is used for cross-platform data exchange and even RPC (via SOAP). As such it is not merely used to store simple data. What Superx++ adds to the mix is the ability to make the XML evolve and adapt dynamically. This is of great benefit as it provides flexibility to the whole system without modifications being made to the XML clients. Currently, this is not possible without Superx++ because Java, C++ and the like all place demands on the XML client to manage the structure of the XML data itself. This is not secure for the special class of data that XML really represents. Neither does this current practice offer flexibility or extensibility in the architecture. What Superx++ provides is a means of encapsulating the XML data within Superx++ objects (which themselves are XML). This forms a special layer or tier in the architecture specially for XML
