Moving_a_Database_Interface_from_Telent_Based_to_a_Web_Clien

Moving a Database Interface from Telent Based to a Web Client Based In order to replace our current database interface with one that is accessed from a web client, we must choose between using an applet or script based system. An applet-based system would require that a compiled binary file be downloaded to and run on the client. This applet would most likely be written in Java. This approach poses several problems. First, a Java compiler would need to be purchased. Secondly, compiled Java applets can be relatively large in size when compared to a web document containing scripts. This would use precious bandwidth on our links to our outlying branches. Lastly, Compiled Java can be resource intensive on the client computer. Some of our computers are getting rather old and do not have the resources to spare. Due to the reasons listed above, the applet-based system must be ruled out. This leaves us with a script-based system. The three most common types of scripting used for this type of application are, Active Server Pages, Java Server Pages and PHP: Hypertext Processor. All three offer similar functionality so the choice must be made using other factors. Active Servers Pages (ASPs) is the most widely used script of this type used today. php, server, java, system, microsoft, similar, pages, need, client, web, support, scripting, project, processor, one, must, jsps, hypertext, hardware, compiled, been, asps, very, using, type, three, scripts, script, resource, requirements, relatively, prove, order, offers, listed