Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revisionLast revisionBoth sides next revision |
scratchpad [2011/06/17 13:07] – drdata | scratchpad [2012/06/15 11:10] – lebbeous |
---|
===this is a test=== | ====== this is a test ====== |
| |
testing | |
| |
| testing |
| [[scratchpad:2012-06-15 This week in]] |
[[#12/15_testing]] | [[#12/15_testing]] |
| |
<p>Work began on Evergreen mid-2004. The later a software system is developed, the more modern practices can be used in that development. Evergreen, for instance, was Web-aware and used <a href="http://en.wikipedia.org/wiki/Unicode">Unicode</a> for text storage and representation from the beginning. To implement these capabilities, Evergreen did not require the costly and difficult rewrites to the foundational code necessary for ILSs that had their basic code written before Unicode had been developed. Unicode is important because it allows a system to handle non-Roman scripts, including characters in Chinese and Arabic.</p> | <p>Work began on Evergreen mid-2004. The later a software system is developed, the more modern practices can be used in that development. Evergreen, for instance, was Web-aware and used <a href="http://en.wikipedia.org/wiki/Unicode">Unicode</a> for text storage and representation from the beginning. To implement these capabilities, Evergreen did not require the costly and difficult rewrites to the foundational code necessary for ILSs that had their basic code written before Unicode had been developed. Unicode is important because it allows a system to handle non-Roman scripts, including characters in Chinese and Arabic.</p> |
| |
<h3>Technology - The Underlying Software Architecture</h3> | <h3>Technology - The Underlying Software Architecture*</h3> |
<p>Evergreen uses a <a href="http://en.wikipedia.org/wiki/Service-oriented_architecture">service-oriented architecture</a> (SOA) with <a href="http://en.wikipedia.org/wiki/REST">representational state transfer</a> (REST) and “n-tier” “<a href="http://en.wikipedia.org/wiki/Multitier_architecture">multiier” architectural</a> design concepts. Let us explore these concepts a bit.</p> | <p>Evergreen uses a <a href="http://en.wikipedia.org/wiki/Service-oriented_architecture">service-oriented architecture</a> (SOA) with <a href="http://en.wikipedia.org/wiki/REST">representational state transfer</a> (REST) and “n-tier” “<a href="http://en.wikipedia.org/wiki/Multitier_architecture">multiier” architectural</a> design concepts. Let us explore these concepts a bit.</p> |
| |
| |
<p>Good luck and welcome to the Evergreen community.</p> | <p>Good luck and welcome to the Evergreen community.</p> |
| <br /> |
| * This section and the next are adapted from an article in the <cite>ASIS&T Bulletin</cite>, December 2008/January 2009, <a href="http://www.asis.org/Bulletin/Dec-08/DecJan09_Molyneux.html">“Evergreen in Context”</a> and used with their kind permission. |
| |
</body> | </body> |
</html> | </html> |