0.
| Previous | Table of Contents | Next |
The fundamental DAIS service from which session objects may be obtained. DAIS::Server would normally be implemented as a persistent
object accessed via the naming service or the trader service. From the DAIS::Server object, the session objects for data access
or alarms & events are created. A client may create as many session objects as wanted.
A session can be created for a view. A view corresponds to a specific hierarchical organization of objects (also called nodes
in this specification). The same object may appear in multiple views and hence in different hierarchical structures. An example
is a breaker appearing in a functional structure (having the function of breaking current) and in a location structure (the
place where it is located), refer also to [10]. Another example is the same object appearing in different areas of authority.
A DAIS server supporting data access may have a number of persistent public groups. Public groups can be used and managed through the group interface, refer to
Section 4.2.7, “DAISGroup IDL,? on page 4-40.
Services that are not implemented will raise the CORBA standard exception NO_IMPLEMENT. Not implemented exceptions can be expected for a data accesssession, an alarms & event session, and inspection.
0.
0.
Figure 3-7 DAIS server IDL in UML