Tamino XML Server Version 9.7
 —  X-Machine Programming  —

Introduction

This introduction summarizes the methods available for programming against the X-Machine using HTTP requests.

The information in this introduction is organized under the following headings:


Accessing Documents in the X-Machine

Tamino's X-Machine can store and retrieve XML documents as well as non-XML documents. In X-Machine terms, XML documents are well-formed XML documents.

X-Machine provides two methods of accessing documents:

Top of page

Storage and Retrieval Format of XML and non-XML Documents

When storing and retrieving documents, the following rules apply:

See the section Media Type Requirements for a description of how Tamino distinguishes between XML and non-XML documents.

Top of page

Security

Security for Tamino databases can be implemented using Tamino's built-in security mechanism that is based on entries in a special collection called ino:security. This is described in detail in the Security section of the documentation for Tamino Manager.

In addition, some limited security mechanisms are offered by the web server if a web server is used as the interface to Tamino. By configuring the web server, protection is possible at the database level. This controls access to databases, using the same mechanism as for ordinary directory structures under the control of the web server.

Note however that security mechanisms based on the web server are limited in use. It is for example not possible to set security at the collection level because XQuery can be used to access data across collection boundaries.

Top of page

The Special Collection ino:etc

If a request is made to store an XML or non-XML document, but the request contains no collection name, the document will be stored in the collection ino:etc. In such cases, XML documents and non-XML documents consisting of text are stored with text retrieval indexing applied to the whole document, and non-XML documents (regardless of whether they consist of text or not) are stored in the special doctype ino:nonXML within ino:etc.

The collection ino:etc is always present in every defined database.

Top of page