Some tools offer you the choice of deploying your applications using any of these options. The Web server and the database function essentially independently of each other. Some products use pooled database connections to attempt to improve server-side performance. In this solution, RAD tool forms can be displayed inside a browser using plug-ins such as PowerBuilder 5.0 or ActiveX controls such as Visual Basic 5.0. The client accesses the database directly, so users need database drivers in addition to the plug-ins or controls, resulting in a much fatter client than with other approaches.
Some products offer middleware that makes the process more efficient by coordinating transactions.
Here, the server renders the look and feel of the interface in HTML and forms built using ActiveX or Java components, or a combination. No database drivers are needed, but users do need to download some components, creating a moderately chubby client, A disadvantage of this method is that not all browsers support different components. This approach offers the widest access for Web users and the thinnest client. The server creates the user interface in standard HTML, Javascript, or both. In the current roundup, Microsoft, Netscape, and Oracle offered this option.