Genoa Active Message MAchine 14-February-2008 (Default branch)


 
Thread Tools Search this Thread
Special Forums News, Links, Events and Announcements Software Releases - RSS News Genoa Active Message MAchine 14-February-2008 (Default branch)
# 1  
Old 02-28-2008
Genoa Active Message MAchine 14-February-2008 (Default branch)

The Genoa Active Message MAchine is a low-latency, high-throughput driver wrapper for the Linux kernel, using Active Ports (a version of Active Messages). It runs parallel to the IP stack and is designed for LANs only.License: GNU General Public License (GPL)Changes:
This release was updated to 2.6.24 and was modified to be installable as a module.Image

More...
Login or Register to Ask a Question

Previous Thread | Next Thread

2 More Discussions You Might Find Interesting

1. Red Hat

microsoft Server 2008 Active authentication to a linux server

Hi, Please could someone advise I'm trying to use winscp from a Window server 2008 R2, but i need to add the authentication key to access the linux rh 5.4 servers ? What is the best way of approaching this ? If there are any web links that could help me do this, that would be good. ... (1 Reply)
Discussion started by: venhart
1 Replies

2. UNIX for Advanced & Expert Users

active machine

HI can any one please tell me how to find the active machine in active/standby architecture , (0 Replies)
Discussion started by: Raom
0 Replies
Login or Register to Ask a Question
CosEventChannelAdmin(3erl)				     Erlang Module Definition					CosEventChannelAdmin(3erl)

NAME
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)