Copyright Notice

The material presented in this site, including any documents, design, text, or information available for viewing or downloading, and within the restrictions and rights imposed by Google, is the copyrighted work of ECE 465 Group 1. Any copying or duplication of site surely constitutes a violation of the GMU honor code, and these activities will be punished to the maximum extent allowed by the GMU Honor Committee. By viewing this site and/or notice, you consent to monitoring and reporting of your browsing activities.  Group 1 reserves the right to immediately alert intelligence agencies of your activities, and you will be subjected to extraordinary rendition or be tried in a military tribunal, unless our ECE 465 professor pleads on your behalf and decides that another reasonable course of action is appropriate.

574days since
Project Presentation

Home‎ > ‎

Overview

Vision

The goal of this project is to explore two commonly used caches methods. These methods include a built-in cache included with every browser or a dedicated caching server for a local network (i.e. proxy server). Client and server processes knowledge will help us develop a protocol that has data communication at its core. Interfacing between the networks and the Internet knowledge helps us with application processes, sockets, and the underlying TCP/IP Protocol.
 

SOW

In order to gain a deeper understanding of the theory and application behind these methods, our team will perform the following:
  • The team will develop a simplified version of both strategies by combining the advantages of local caching and network applications
  • The team will develop socket programming  to represent an understanding of the client and server and P2P processes, interfaces and messages between processes, and performance statistics
  • The team will document the principles of operations, protocols required for message exchange, and the protocol implementation
  • The team will comply with the automatic and manual operations needed for demonstration and testing via a GUI interface
  • The team will submit a final report that documents all design phases, implementation and project management activities
  • The team will build and maintain a project website that includes progress updates, milestones, documentation, and project issues

 Requirements

For a more detailed description of the project, please visit our professor's project website. You can also refer back to the Documentation page for additional information.