tnaps การใช้

• This concept is a further development of business object approach from TNAPS 2.
• TNAPS uses . NET Remoting for network communications.
• TNAPS focuses on business logic implementation.
• However, developer can extend TNAPS with WCF or any other hosting technology through hosting provider extension.
• On June 9, 2011 TN reported that TNAPS 3 is being in the early beta-testing process.
• New major version of TNAPS application server uses component-driven approach and application can be created by combining existing components.
• TNAPS 3 features . NET and Mono compatibility as well as multiple operation systems support : Windows, Linux and Mac OS X.
• Developer applies principle of decomposition and splits server side logic into set of components ( called " business objects " in TNAPS ).
• The main principle of TNAPS is that a developer has to write business logic only and would be able to host it and set user access policy, database parameters and other configuration without writing code  just by existing component reusage.
• After finishing set of business objects development they should be arranged into " Bizlet "-one server application instance in TNAPS . Bizlet contains business objects, database configuration, user access permissions and hosting parameters ( i . e . IP address and port to listen ).