KiranAnna - A REPORT ON THE PROJECT EVENT NOTIFICATION...

Info iconThis preview shows pages 1–5. Sign up to view the full content.

View Full Document Right Arrow Icon
A REPORT ON THE PROJECT EVENT NOTIFICATION SERVER By Kiran Anna Temitope Alo Submitted as part of the requirements of the course “Process Coordination in Service and Computational Grids”, CPA5937 Professor Dr. Dan Marinescu Department of Computer Science University of Central Florida Spring 2002
Background image of page 1

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
Table of Contents 1. Introduction…………………………………………………………………. .3 2. Event Notification Service Mechanisms. .……………………………………5 3. ENS design…………………………………………….……………………. .7 2
Background image of page 2
1. INTRODUCTION 1.1 Bond Bond is a Java-based object-oriented middleware for network computing. Network computing is a paradigm that emphasizes the use of network resources, computing resources distributed across the network, over local resources. Network resources are hosts, programs and data. Middleware is a software layer that allows developers to mold systems tailored to specific needs from components and develop new components based upon existing ones. The goals of the Bond system are to: Facilitate access to network resources, Support collaborative activities, and Accomodate software diversity and hardware heterogeneity. Bond can be used in stand-alone mode or to connect to a Bond domain. A Bond domain consists of a society of users with common interests and a number of services. In stand-alone mode a user may create objects and agents and execute locally several demos. To create a Bond domain one needs to activate the servers provided with the package. 1.2 Problem and Motivation In order to support collaborative activities, the Bond needs a service mechanism that supports coordination of the work over the network. A notification service based on events provides a good solution to this problem. This service can be implemented by means of an Event Notification Server (ENS) added to the Bond domain. This model consists of two types of users- event producers and event consumers. The producers register events with the ENS and the consumers subscribe to the events in the ENS. The ENS coordinates the events between the producers and the consumers. The ENS design is explained in more detail in chapter 2. 3
Background image of page 3

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
1.3 ENS Mechanisms – A Background The primary purpose of an event notification service is to support notification selection and delivery. The challenge we therefore face is maximizing expressiveness in the selection mechanism and scalability in the delivery mechanism. Expressiveness is the ability of the event service to provide powerful data model to express filters and patterns on notifications and to use that data model as the basis for optimizing the notification delivery. Scalability measures are not just related to number of event generators, number of event notifications, and number of notification recipients, but alongside, it identifies issues related to local-area networks in terms of latency, bandwidth, centralized control etc. The efficiency and performance of the event service and the routing of notification is
Background image of page 4
Image of page 5
This is the end of the preview. Sign up to access the rest of the document.

Page1 / 13

KiranAnna - A REPORT ON THE PROJECT EVENT NOTIFICATION...

This preview shows document pages 1 - 5. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online