A
agent_008_nl
Guest
I can recommend autoedge thefactory. You would need some time to get it to work and understand how it works. To me it proved a valuable investment of my time. See for an introduction community.progress.com/.../879.welcome-to-the-complete-autoedge-kit.aspx you can find code at github.com/.../autoedgethefactory but of course Peter can provide the most useable links. These were quickly grabbed. You can see oera as a separation of concerns principle ( robertcorvus.com/separation-of-concerns-principle ) at a high level. "The value of separation of concerns is simplifying development and maintenance of programs. When concerns are well-separated, individual sections can be reused, as well as developed and updated independently. Of special value is the ability to later improve or modify one section of code without having to know the details of other sections, and without having to make corresponding changes to those sections." Of course oera is not much more than a rebranding of principles described before, outside of the progress world. I have no idea where you can find a white paper going a bit into depth about oera. This paper from outside the psc world could give you an idea: www.ambysoft.com/.../persistenceLayer.pdf (doubtless much more to be googled). So if you separate your application into the layers used in the oera you should be able to switch UI's more easily / connect different UI types simultanuously to your backend. Have different programmers/teams work on different layers more or less independently (using the api of the layer below that for the rest can be regarded as a black box). Allas you will find the progress database, as db type, tightly tied to your dataaccess layer when you use it's propietory (but very handy) query language. But at least only to that layer if you implement the separation well. It would be nice if we could replace the db easy with f.e. an open source db like postgresql. -- Kind regards, Stefan Houtzager Houtzager ICT consultancy & development www.linkedin.com/in/stefanhoutzager
Continue reading...
Continue reading...