User:Sly182/TNAPS Application Server
| Developer(s) | Technovation Ltd. |
|---|---|
| Initial release | 10 December 2009 |
| Stable release | 2.0.5
/ October 22, 2010 |
| Written in | .NET |
| Operating system | Windows |
| Type | Application server |
| License | Freeware |
| Website | http://www.technovation.ru/tnaps |
TNAPS is a freeware .NET application server. It is based on the concept of application business logic separation into middleware layer. This is also called three-tier software architecture. Althought, there are many application servers for Java platform, there are only a few for .NET. The main principle of TNAPS is that 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.
Current version of TNAPS requires .NET 3.5 sp1.
Basics[edit]
TNAPS focuses on business logic implementation. Developer applies principle of decomposition and splits server side logic into set of components (called business objects in TNAPS). The main idea behind this decomposition is to get business objects that provide some value to the end-user (the one using client application).
Developer defines business objects contracts for accessing created server functionality and implement client application using contracts.
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).
Developer or end-user of the TNAPS application can decide what kind of logic provide to the respective use by granting / rewoking access to particular business object.
Business objects access permisions are defined at the user group level.
Features[edit]
- Development of three-tier applications is straightforward.
- Developer has no problems with hosting, security, channel encryption, user access management etc.
- Windows administrators-oriented management console (MMC snap-in).
- User can switch between database server types without rewriting code.
- TNAPS supports all .NET languages.
- Database access technologies - all available in .NET : ADO.NET, LINQ, EDM
- All logic written for local TNAPS server can be migrated to cloud hosting providers like Amazon EC2 without rewriting.
- Extensibility - almost every part of the server can be extended by user.
Management[edit]
TNAPS configuration is done withing TNAPS Management Center (or Console). It is a snap-in for Microsoft Management Console.
Hosting[edit]
TNAPS uses .NET Remoting for network communications. That means that client application can be implemented using .NET or Mono platform only. However, developer can extend TNAPS with WCF or any other hosting technology through hosting provider extension.
TNAPS Remoting Host Provider has some advanced (comparing to standart .NET Remoting) features: Channel Encription, Traffic Signing and Traffic Compression.
Licensing & Pricing[edit]
TNAPS is freeware, proprietary application server.
See also[edit]
Other .NET application servers: