Simple Event Notification System Environment (SENSE)
Abstract: The Simple Event Notification Service Environment (SENSE) is a client-server communciation service technology for computer networks that enhances the organization and delivery of asynchronous status information. In its simplest form, SENSE is a reliable clearinghouse and delivery service for event notices.
Notes on the condition of the document:
- This is a very early, partial release of information about the SENSE facility.
- Some segments of the documentation are outlines only, that is, they contain headings to indicate the intended content, but no content.
- Overview sections contain some content to familiarize the reader with the concepts surrounding SENSE and its client interface.
- Some appendices include introductory or partial information to give the reader a few concrete examples of the objects and properties that SENSE manipulates.
- The documents are being distributed in HTML so that they may be viewed online using and printed from almost any desktop platform today.
- Technical details such as property names and values, function names and argument lists, etc., are subject to change without warning.
- The file structure of the document is certain to change. The final form will comprise many more, smaller files. It may even include a number of diagrams and charts to clarify configurations and protocol exchanges.
- Comments and flames to the authors, please.
Table of Contents:
Introduction and Architecture
Introduction and Overview
Elements of the System
[Client interface headings to be inserted here]
SENSE Client API, call interface spec
The Server's Publication
Editions of Publications
Server Management Properties
The SNMP.TRAP Edition
The Minimal Edition of a Publication
Server-Supplied Properties in Event Messages
Condition Codes for Publications
Classes of SENSE Publications
Spec of Simple Text Event Protocol (STEP) Edition
Glossary of Terms
Copyright (C) 1996 by Richard Landau & Jay Martin. All rights reserved.
Comments and flames to the authors. "Why use rational argument when there's a flamethrower handy?" Hey, go ahead. We didn't exactly leave the gloves on when we wrote this. Richard Landau (firstname.lastname@example.org) & Jay Martin (email@example.com) using that sterling tool, HTML Author. Last modified 96/05/19.