The Beginning

Work on TAS traces back to mid 1993. Wow, that far back you say? Yes, I do this in my spare time. And by the way I do actually have a life outside of computers. Additionally during this time the switch from functional languages to OO had occurred. And from 3rd generation languages to 4gmls. So during this period of history we have learned a lot in IT. Due to this there has been various refactoring involved in TAS to make use of the new technologies and ideas that have come along.

Events of interest for TAS

Work on prototyping infrastructure for a customer service app in 1993 forms basis for TCP/IP communication frameworks.
Work on a startup ISP provides insight into middlewhere servers and RPC technologies
On the side efforts for bottom level frameworks of logging, configuration management, messeging, and RPC lead to initial conceptual C server implementation.
Project for replacement of a billing system provides opportunity to expand and complete initial C server implementation.
Interest in learning the Java programming language leads to conversion and update of initial C server implementation libraries into OO and the java world in 1999.
Experience in J2EE applications causes a shift in object endpoint request mapping paradime. Additionally the transition of doing web stuff from a C implementation to a java implementation drives the implementation in java to follow the now more formalized J2EE Servlet specification. (Cerca 2002).
Implementation of a lookup service and a distributed routing service more mature than previous implementation causes core library loading to be re-evaluated. Load up switched to a mbean like loading pattern in 2004.
Refactoring of the thick client simulation implementation to client-server on top of TAS forces construction of a J2EE like application loading concept. The concept of applications, as well as application deployment and multi-classloaders was introduced in 2005.
The desire to finalize the new SRS websight causes a hard code demarcation. TAS 2.0 is cut.