costime(3erl) [linux man page]

cosTime(3erl)						     Erlang Module Definition						     cosTime(3erl)

NAME

       cosTime - The main module of the cosTime application

DESCRIPTION

       To get access to the record definitions for the structures use:
       -include_lib("cosTime/include/*.hrl").

       This module contains the functions for starting and stopping the application.

       This application use the time base 15 october 1582 00:00 . Performing operations using other time bases will not yield correct result.

       The  OMG  CosTime  specification defines the operation secure_universal_time . As of today we cannot provide this functionality considering
       the criteria demanded to fulfill the OMG specification.

       When using this application, time and inaccuracy supplied by the user must be given in number of 100 nano seconds . The	Time  Displacement
       Factor is positive east of the meridian, while those to the west are negative.

       This application use calender:now_to_universal_time(Now) to create a UTC. Hence, the underlying OS must deliver a correct result when call-
       ing erlang:now() .

       When determining the inaccuracy of the system, the user should consider the way the time objects will be  used.	Communicating  with  other
       ORB's, add a substantial overhead and should be taken into consideration.

EXPORTS

       install_time() -> Return

	      Types  Return = ok | {'EXIT', Reason}

	      This operation installs the cosTime Time Service part application.

       uninstall_time() -> Return

	      Types  Return = ok | {'EXIT', Reason}

	      This operation uninstalls the cosTime Time Service part application.

       install_timerevent() -> Return

	      Types  Return = ok | {'EXIT', Reason}

	      This operation installs the cosTime Timer Event Service part application.

   Note:
       The Timer Event Service part requires Time Service part and cosEvent or the cosNotification application to be installed first.

       uninstall_timerevent() -> Return

	      Types  Return = ok | {'EXIT', Reason}

	      This operation uninstalls the cosTime Timer Event Service part application.

       start() -> Return

	      Types  Return = ok | {error, Reason}

	      This operation starts the cosTime application.

       stop() -> Return

	      Types  Return = ok | {error, Reason}

	      This operation stops the cosTime application.

       start_time_service(Tdf, Inaccuracy) -> Return

	      Types  Tdf = short()
		     Inaccuracy = ulonglong(), eq. #100 nano seconds
		     Return = ok | {'EXCEPTION', #'BAD_PARAM'{}}

	      This operation starts a Time Service server. Please note that there may only be exactly one Time Service active at a time. The Inac-
	      curacy parameter defines the inaccuracy the underlying OS will introduce. Remember to take into account latency  when  passing  time
	      object between nodes.

       stop_time_service(TimeService) -> ok

	      Types  TimeService = #objref

	      This operation stops the Time Service object.

       start_timerevent_service(TimeService) -> ok

	      Types  TimeService = #objref

	      This  operation  starts  a  Timer  Event Service server. Please note that there may only be exactly one Timer Event Service per node
	      active at a time. The supplied TimeServcie reference will be the object Timer Event Service contacts to get access to a new UTC.

       stop_timerevent_service(TimerEventService) -> ok

	      Types  TimerEventService = #objref

	      This operation stops the Timer Event Service object.

Ericsson AB							  cosTime 1.1.10						     cosTime(3erl)

Check Out this Related Man Page

CosEventChannelAdmin_EventChannel(3erl) 		     Erlang Module Definition			   CosEventChannelAdmin_EventChannel(3erl)

NAME

       CosEventChannelAdmin_EventChannel  -  This  module  implements an Event Channel interface, which plays the role of a  mediator between con-
       sumers and suppliers.

DESCRIPTION

       An event channel is an object that allows multiple suppliers to communicate with multiple consumers in  a  highly  decoupled,  asynchronous
       manner.	The event channel is built up incrementally. When an event channel is created no suppliers or consumers are connected to it. Event
       Channel can implement group communication by serving as a replicator, broadcaster, or multicaster that forward events from one or more sup-
       pliers to multiple consumers.

       It  is  up to the user to decide when an event channel is created and how references to the event channel are obtained. By representing the
       event channel as an object, it has all of the properties that apply to objects. One way to manage an event channel is to register it  in  a
       naming context, or export it through an operation on an object.

       To get access to all definitions include necessary hrl files by using:
       -include_lib("cosEvent/include/*.hrl").

       Any object that possesses an object reference that supports the ProxyPullConsumer interface can perform the following operations:

EXPORTS

       for_consumers(Object) -> Return

	      Types  Object = #objref
		     Return = #objref

	      This operation returns a ConsumerAdmin object reference. If ConsumerAdmin object does not exist already it creates one.

       for_suppliers(Object) -> Return

	      Types  Object = #objref
		     Return = #objref

	      This operation returns a SupplierAdmin object reference. If SupplierAdmin object does not exist already it creates one.

       destroy(Object) -> Return

	      Types  Object = #objref
		     Return = #objref

Ericsson AB							  cosEvent 2.1.10			   CosEventChannelAdmin_EventChannel(3erl)

Linux and UNIX Man Pages

costime(3erl) [linux man page]

Check Out this Related Man Page