ADU.Suspend
This method is useful for applications that need to know how names were generated, especially for applications that make repeated use of the + token and need to be able to go back and fill in values in the various subcontainers they have created.
The following fields are restricted and cannot be changed by applications:
aduidtermination
transfercountduration
createtimeupdate_time
endtime
Setting values can generate watch, change, and drop events.
Input Parameters
aduid | An ADUID. |
data | Values to be set, not to exceed 1023. |
Output Parameters
newnames | List of names created to resolve container names. |
ADU.Suspend
IDL Syntax ORBStatus Suspend( in string aduid ) ;
Description Like Terminate, this removes the caller's session from the ADU's session list, but it does not remove the loginid from the owner's list. Use this when your application is done with the ADU for now, but intends to do more work on it later. This method gives permission for the ADU server to retire the ADU to the DUStore, on the grounds that it may not be accessed for some time.
ADU.Terminate
IDL Syntax ORBStatus Terminate( in ADU_ID aduid ) ;
Description When a client creates, reads, modifies, or transfers an ADU, the client's name and session is added to internal lists. When the Terminate method is invoked, the client's name and session is removed from
the lists for that ADU. When the of names is empty, the ADU is purged from the system and is used for reporting. When the list of sessions is empty but the list of names is not (this can occur if Suspend is used), the ADU may be moved to the DUStore for temporary storage.