Databases Reference
In-Depth Information
incubator technology in Zend Framework and provides both a persistence data
access layer as well as an API for managing XML data easily.
In this section, we provide an architectural overview of the XCS. We describe
each of the components that makes up the XCS, and we explain how they work
together. Figure 3-3 illustrates the XCS architecture.
Figure 3-3 XCS architecture overview
XMLContent (Zend_Db_Xml_Content)
As a developer, you can encounter XML data in many forms, such as Web
services messages, RSS/Atom feeds, and configuration files. Once you decide
that this XML data needs to be saved somewhere, we can assume several things
about this data:
First, we need a way to uniquely identify it, so that once it is saved, it can
easily be programmatically found and retrieved. The unique name can be a
numeric ID or a user-provided name.
The second assumption is that the XML data will be stored “as is”. It will not
be modified or changed in any way. Any modifications that are required will
be made by the application outside of the XCS. Internally, the XML data is
stored as a DOM document, but an application is free to access the data as a
file stream, string, or several other convenient access methods which can or
cannot be implementation-dependent.
Third, the capability is provided to add additional metadata about the XML
data that is saved. For example, if the XML data is a blog entry, perhaps the
Search WWH ::
Custom Search