• Background
• CLASS Project
• CLASS Staff
• General Insights
• Questions & Considerations
• Content
• Development Teams
• Content Acquisition
• Assessment & Grading
• Design
• Introduction
• Modeling
• Presentation
• Interactivity
• Navigation
• Assessments
• National Standards
• Quality Assurance
• Courses
• Features
• Courses
• Copyrights
• Technology
• Building a Course
• See and Say
• There are Limits!
• Influence and Change
• CLASS Courses
• Content
• Extras Designed
• Extras Linked
• Class Assessments
• A Bit of Dreamweaver
• Proofing
• Graphics
• MOUs
• Detailing Treatment
• Course Credits
• CLASS Style
• Publications

Server-side versus Client-side Technology

Peripheral concerns: firewalls, proxies, borders, cost of personnel to support, both in terms of establishing the software on your end and the technological expertise on the user's end

CLASS™ started with client-side technology. This required that students have access to an installation program for their computer. A CD was distributed to students that put necessary files on their machine. It was cumbersome, especially for home-schoolers with no technical expertise. It was not an easy process in 1995!

By 1998, the installation piece was moved to the server. This accommodation helped the learning centers and schools with their firewall and proxy issues. It made the startup for a given student less cumbersome. But it also meant that a student could not work offline. One of the original concepts of the CLASS™ research project was to allow a student to log in, work off line, then log back in so their machine and the server could update each other. This is another serious lesson in getting to know your audience.

Copyright 2004 - University of Nebraska Board of Regents - All Rights Reserved