| Strengths | Weaknesses | |
|---|---|---|
|
data remains on a central server and is current whenever users are accessing "thin" client little desktop support beyond browser and necessary "plug-ins" GUI many users already using Web browsers for other purposes cross platform support easier (if application designed carefully) good possibilities for integration of multi-media elements into an application, including educational material and resources out on the Web |
application development tools still difficult to select in a still-expanding marketplace performance likely not be as good as other options requires a robust TCP/IP network to function properly printer support may be difficult for some kinds of web pages may be difficult to maintain "state" (i.e., sense of a continuing browser to server session) three tier architecture (browser, web/application server, data server) may be difficult to develop and support requires more robust data and application servers than may be currently deployed |