OSF DCE Administration Guide--Core Components

OSF DCE Administration Guide—Core Components
TABLE 32-2. Encoding Types
____________________________________________________________________
Encoding Type Meaning
____________________________________________________________________
____________________________________________________________________
Not implemented in this release of DCE.any
____________________________________________________________________
The attribute value must be a list of attribute type UUIDs
enclosed in braces. This encoding type defines an attribute
set. Attribute sets allow for easier attribute search and
retrieval. For instance, a query on an attribute set returns all
instances of attributes that are members of the set.
attrset
____________________________________________________________________
The attribute value must consist of authentication,
authorization, and binding information suitable for
communicating with a DCE server. Use this encoding if you
want to store a name or server binding as an object’s attribute.
See Section 32.3.2.2 for more information.
binding
____________________________________________________________________
The attribute value must be a string of bytes. The byte string
is assumed to be a pickle or is otherwise a self-describing
type. Note that this encoding type allows entry of binary data.
See the xattrschema(8dce) reference page for more
information on entering binary data.
byte
____________________________________________________________________
Not implemented in this release of DCE.confidential
____________________________________________________________________
The attribute value must be an internationalized string of
bytes with a tag identifying the OSF registered codeset used
to encode the data. Note that this encoding type allows entry
of binary data. See the xattrschema(8dce) reference page for
more information on how to enter binary data.
i18ndata
____________________________________________________________________
The attribute value must be a signed 32-bit integer.integer
____________________________________________________________________
The attribute instance value must be a character string
printable by the PCS.
printstring
____________________________________________________________________
The attribute value must be an array of one of more
printstrings. Note that the printstring can be a null.
stringarray
____________________________________________________________________
The attribute value must be a DCE UUID.uuid
____________________________________________________________________
The attribute has no value. It is simply a marker that is either
present or absent.
void
____________________________________________________________________
32.3 DeÆning Attribute Trigger Servers
Some attribute types require the support of an outside server either to verify input
attribute values or to supply output attribute values when those values are stored in an
external database. Such a server could, for example, connect a legacy registry system to
the DCE registry. The attribute trigger facility provides for automatic calls to outside
DCE servers, known as attribute triggers.
32 − 8 Tandem Computers Incorporated 124243