Overview Component Architectures It has been a number (Top web site)
Overview Component Architectures It has been a number of years since the idea of multitier server-side deployments surfaced. Since then, more than 50 application servers have appeared on the market. At first, each application server provided component services in a nonstandard, proprietary way. This occurred because there was no agreed definition of what a component should be or how it should be provided with services or how should it interact with the application server. The result? Once you bet on an application server, your code was locked into that vendor s solution. This greatly reduced portability and was an especially tough pill to swallow in the Java world, which promotes openness and portability. What we need is an agreement, or set of interfaces, between application servers and components. This agreement will enable any component to run within any application server. This will allow components to be switched in and out of various application servers without having to change code or potentially even recompile the components themselves. Such an agreement is called component architecture and is shown in Figure 1.2. If you re trying to explain components to a nontechie, try these analogies: Any CD player can play any compact disc because of the CD standard. Think of an application server as a CD player and components as compact discs. In the United States, any TV set can tune into any broadcast because of the NTSC standard. Think of an application server as a TV set and components as television broadcasts. Application Server agreed-upon interfaces specified by component architecture Components Figure 1.2 A component architecture.
Get account with us and you will get completely access to our free web templates database with over 10.000 templates in it to build your website.Don’t wait, go and check free web templates.