Includes AutoEdge and any future reference implementations of the OpenEdge® Reference Architecture
At Exchange 2007, a session entitled "Mashup Basics" was presented. In that session, we demonstrated the ability to add value to an OpenEdge application by 'mashing up' content from other sources. The examples we used were aggregated RSS feeds from Yahoo Pipes and a Google Map.
As many people are familiar with the OERA reference application (AutoEdge), we used it as the vehicle per se to demonstrate this capability.
Attached is a zip file with the modified code and instructions on how to implement this demo enhancement into your version of AutoEdge.
The OpenEdge Reference Architecture (OERA) describes an overall structure and pattern for the architecture of modern applications, but does not in itself specify any particular implementation. Progress Software (PSC) has generated a series of whitepapers over recent years which discuss various aspects of this architecture with some sample code, but this code is limited in scope and there is no pretense of it illustrating production-ready techniques. More recently, PSC introduced AutoEdge, an “application example” meant to illustrate one way in which OERA principles might be applied in a real application, but it too is built on a number of simplifying assumptions and does not pretend to offer production ready code on which customers might build real systems without significant further work.
This sample code complements John Sadd's white paper Implementing the OpenEdge® Reference Architecture: 8: Context Management.
By default, AutoEdge uses a "very" optimistic locking approach. That is, all changes are saved to the database without first checking to see if the modified record has in fact been changed. Here is one example of how optimistic locking could be implemented in AutoEdge.
The attached zip contains scripts and instructions on how to setup OpenEdge Replication and OpenEdge Management with AutoEdge.
PSC has created AutoEdge as an example application example to illustrate the OpenEdge Reference Architecture. The idea and purpose of AutoEdge is to provide practical definition and examples of OERA and illustrates many aspects of modern ABL and Sonic code and technique. AutoEdge is what an application, with certain ‘business requirements’, might look like if architected and designed following the OERA guidelines.