Visit The New, Modern Unix Linux Community

Linux and UNIX Man Pages

Test Your Knowledge in Computers #443
Difficulty: Easy
FHM, a men's lifestyle magazine, asked 1,344 women if they preferred to hang out with a computer science expert or a footballer, and 1,023 (76.116%) stated they preferred geeks over athletes.
True or False?
Linux & Unix Commands - Search Man Pages

eventc(1) [debian man page]

EVENTC(1)																 EVENTC(1)

eventc - create a CORBA EventChannel and register it in the naming service SYNOPSIS
eventc [-n channel-name] [-N factory-name] [-c nanoseconds] [-i id] [-p num] [-q num] [-R milliseconds] [-t repository-id] [-vh] [-ORBparameter value] [factory-uri] DESCRIPTION
eventc contacts the omniEvents server to request an Event Channel. The Event Channel is created within the the omniEvents process. eventc then registers the created Event Channel with the Naming Service, and exits. factory-uri: The factory may be specified as a URI. This may be an IOR, or a corbaloc::: or corbaname::: URI. Example: eventc corbaloc::localhost:11169/omniEvents If the factory-uri argument is not supplied, then the -N factory-name option is used to look up the server in the CORBA Name Service. OPTIONS
-n channel-name Sets the CORBA Name Service name for the new EventChannel CORBA object. Format for channel-name: [CONTEXT-ID[.CONTEXT-KIND]/]*OBJECT-ID[.OBJECT-KIND] Examples: foo,,, foo/bar/baz.qux. The default is EventChannel -N factory-name The CORBA Name Service name for the EventChannelFactory CORBA object. The default value is EventChannelFactory. This value is only used when the factory-uri argument is not supplied. -c nanoseconds Sets the CyclePeriod_ns parameter of the new event channel. -i id Set the InsName of new event channel, to enable access via corbaloc. -p num Sets the MaxNumProxies parameter of the new event channel. -q num Sets the MaxQueueLength parameter of the new event channel. -R milliseconds Sets the PullRetryPeriod_ms parameter of the new event channel. -t repository-id Sets the FilterId parameter of the new event channel. -v Output the CORBA IOR of the new EventChannel CORBA object. -h Display a short summary of command-line options. -ORBparameter value Standard omniORB options. see omniORB documentation for details. This option is commonly used to set the omniORB traceLevel, in or- der to get more detailed output. Example: -ORBtraceLevel 5 ENVIRONMENT VARIABLES
OMNIORB_CONFIG The location of the omniORB configuration file. COPYRIGHT
Copyright (C) 2003-2005 Alex Tingle, 1999 Paul Nader. This is free software; see the source for copying conditions. There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICU- LAR PURPOSE. EVENTC(1)

Check Out this Related Man Page

CosEventChannelAdmin(3erl)				     Erlang Module Definition					CosEventChannelAdmin(3erl)

CosEventChannelAdmin - The CosEventChannelAdmin defines a set if event service interfaces that enables decoupled asynchronous communica- tion between objects and implements generic (untyped) version of the OMG COSS standard event service. DESCRIPTION
The event service defines two roles for objects: the supplier role and the consumer role. Suppliers supply event data to the event channel and consumers receive event data from the channel. Suppliers do not need to know the identity of the consumers, and vice versa. Consumers and suppliers are connected to the event channel via proxies, which are managed by ConsumerAdmin and SupplierAdmin objects. There are four general models of communication. These are: * The canonical push model. It allows the suppliers of events to initiate the transfer of event data to consumers. Event channels play the role of Notifier . Active suppliers use event channel to push data to passive consumers registered with the event channel. * The canonical pull model. It allows consumers to request events from suppliers. Event channels play the role of Procure since they pro- cure events on behalf of consumers. Active consumers can explicitly pull data from passive suppliers via the event channels. * The hybrid push/pull model. It allows consumers request events queued at a channel by suppliers. Event channels play the role of Queue . Active consumers explicitly pull data deposited by active suppliers via the event channels. * The hybrid pull/push model. It allows the channel to pull events from suppliers and push them to consumers. Event channels play the role of Intelligent agent . Active event channels can pull data from passive suppliers to push it to passive consumers. To get access to all definitions, e.g., exceptions, include necessary hrl files by using: -include_lib("cosEvent/include/*.hrl"). There are seven different interfaces supported in the service: * ProxyPushConsumer * ProxyPullSupplier * ProxyPullConsumer * ProxyPushSupplier * ConsumerAdmin * SupplierAdmin * EventChannel Ericsson AB cosEvent 2.1.10 CosEventChannelAdmin(3erl)

Featured Tech Videos