Web application: Difference between revisions

Revision as of 11:52, 16 September 2007

Revision as of 14:16, 20 September 2007

Line 14:

A significant advantage of building Web applications to support standard browser features is that they should perform as specified regardless of the operating system or OS version installed on a given client. Rather than creating clients for [[Microsoft Windows|MS Windows]], [[Mac OS X]], [[Linux|GNU/Linux]], and other [[operating system]]s, the application can be written once and deployed almost anywhere. However, inconsistent implementations of the [[HyperText Markup Language|HTML]], [[Cascading Style Sheets|CSS]], [[Document Object Model|DOM]] and other browser specifications can cause problems in web application development and support. Additionally, the ability of users to customize many of the display settings of their browser (such as selecting different font sizes, colors, and typefaces, or disabling scripting support) can interfere with consistent implementation of a Web application.

Another (less common) approach is to use [[Adobe Flash]] or [[Java applet]]s to provide some or all of the user interface. Since most Web browsers include support for these technologies (usually through plug-ins), Flash- or Java-based applications can be implemented with much of the same ease of deployment. Because they allow the programmer greater control over the interface, they bypass many browser-configuration issues, although incompatibilities between Java or Flash implementations on the client can introduce different complications. Because of their architectural similarities to traditional client-server applications, with a somewhat "thick" client, there is some dispute over whether to call systems of this sort "Web applications"; an alternative term is "[[Rich Internet Application]]".

==Structure==