The OpenEdge Hive - OERA Infrastructure

Exception Handling Service

tamhas — Sun, 31 Aug 2008 18:30:32 +0000

Bruce Gruenbaum:
Let me start out by saying that this is service that hitherto has not worked as well for me in OpenEdge as it does in Java/.NET. In a nutshell, it is a service that is responsible for receiving exceptions that have been caught somewhere. The Exception Handling Service receives the exception, logs it to an exception log and then looks for a class that has been designed to process the exception in some way. The trick is to have a standard way of processing all exceptions so that the user never experiences a Java/C#/OpenEdge exception/error condition that has not been handled.

OERA Group

Auditing Service

tamhas — Sun, 31 Aug 2008 18:28:37 +0000

Bruce Gruenbaum:
The Auditing Service logs access and changes to data and stores away the state of the data at the time that an event took place. It is subtly different from logging in that logging is about keeping track of the fact that things happened whereas auditing is about keeping track of exactly what happened.

Thomas Mercer-Hursh:

OERA Group

Caching Service

tamhas — Sun, 31 Aug 2008 18:26:54 +0000

Bruce Gruenbaum:
The Caching Service is responsible for storing data that may be referred to at a future point in time by this physical session and thereby reduce processing time. Caching with OpenEdge is simply a store of data. In muti-threaded environments, the cache can be self cleaning based on a LRU algorithm or something similar.

Thomas Mercer-Hursh:

OERA Group

Content Management Service

tamhas — Sun, 31 Aug 2008 18:22:43 +0000

Bruce Gruenbaum:
The Context Management Service is designed to keep track of data that is needed to reestablish a logical session's context on subsequent interactions with a target. People will argue whether context should be stored on the client or the server or both. In my experience, a framework has to provide support for all three options - client, server and both. If one views a set of interactions with a set of targets as a set conversations, context management is about determining where you last left off in the conversation with a specific target.

Thomas Mercer-Hursh:

OERA OSI Group

Session Management Service

tamhas — Sun, 31 Aug 2008 18:20:06 +0000

Bruce Gruenbaum:
Session Management and Context Management are closely related but subtly different. A client may have many connections to several different targets. Each of those connections may be termed a session and its lifetime is the duration of the connection. That is a physical session. Many times though, the client makes repeated connections to a target and often to more than one target at a time. It may often be possible to reduce the amount of processing time involved by reusing an authentication token. Thus a logical session may span many connections to many different targets. The Session Manager is responsible of tracking data that is related to the logical session.

OERA Group

Logging Service

tamhas — Sun, 31 Aug 2008 18:14:34 +0000

Bruce Gruenbaum:
The Logging Service logs every event that takes place in the system that is set to be logged. On a Windows platform these logs are optionally written to the Event Log. Where such services exist on other platforms they are used as appropriate. Exceptions are automatically logged with their complete stack traces.

Thomas Mercer-Hursh
"set to be logged" seems to imply getting configuration data on what to log.

OERA OSI Group

General Principles

tamhas — Fri, 29 Aug 2008 22:52:06 +0000

This section will be used to provide general guidelines for the operation and construction of components for this project.

OERA OSI Group

OERA OSI Project

tamhas — Fri, 29 Aug 2008 22:43:06 +0000

This is the project for tracking work on the OERA Open Source Initiative. Use it for feature requests, issue tracking, bug reports and the like. Use the forum for general discussion and add comments to individual pages of content as appropriate.

OERA OSI Group

OERA Open Source Initiative

tamhas — Fri, 29 Aug 2008 21:55:55 +0000

The OERA Open Source Initiative (OERA OSI) is a project to define, create, and refine a series of production quality components which can serve as a sound basis for those creating their own OERA implementations. The primary focus will be components which would form a portion of the Common Infrastructure portion of the standard OERA model, but we will not exclude contributions for other sorts of helper classes which might be used as part of a Data Access, Business Logic, or UI layer.

OERA Group