Siemens V 4.0 User Manual

GINA V4.0 System Administrator Guide – September 2000

203

Dr

uc

k v

om 24. 01.2001 17:01.05

 f

achw

or

t

A number of remote subcalls can be started in the T-ORB procedure “action point”.
Given that the

→

server process is subsequently released, an action point is always a

potential

→

end of transaction, a potential

→

monitoring and restart point.

The results of all subcalls are evaluated by the

Continuation

of the action point. The

continuation is a parallel callback which is only started when all the results have been
received.

A

→

client cannot recognize whether the

→

server is carrying out an action point. A

server cannot recognize whether it was called from an action point.

see

→

server

The parsers of the GINA development systems sometimes need more information than
can be formulated in C++. GINA comments are used for this purpose. They are ignored
by the compiler but not by the GINA parsers. These comments contain a sequence of
expressions that are referred to as annotations.

A GINA application is a transaction-monitored application under T-ORB. A GINA appli-
cation can include a number of

→

server processes. A non-transaction-monitored appli-

cation can be connected to a transaction-monitored application using T-ORB/Client.

When you use the T-ORB procedure “asynchronous call”, the

→

client does not wait for

the call to be executed and the result returned. Possible results are thus discarded (see
also

→

notification).

Under T-ORB, even asynchronous requests/calls undergo transaction monitoring, i.e.
they are executed in an independent transaction

 a successful end of transaction

(commit). The asynchronous call under T-ORB is a relative

→

time request with zero

delay.