Difference: CourseModules (1 vs. 2)

Revision 22011-05-10 - DonaldActon

Line: 1 to 1
 
META TOPICPARENT name="ComputerScience317Cwsei"
Deleted:
<
<
 -- DonaldActon - 09 May 2011

One possible way to organize the course is to break it down into a collection of modules of about a week. Each module will some number of the following associated with it

Line: 36 to 35
 
  • Naming/Discovery
  • Stream vs Messages
  • P2P
Added:
>
>
  • Pipelining to improve BW utilization over stop and go
 

Revision 12011-05-09 - DonaldActon

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="ComputerScience317Cwsei"

-- DonaldActon - 09 May 2011

One possible way to organize the course is to break it down into a collection of modules of about a week. Each module will some number of the following associated with it * A set of learning outcomes * Readings/videos * Class activities * Assignments, homework * Assessment mechanisms

A list of possible modules (sub-bullets are hints at what the main bullet might cover) :

  • Bandwidth and Latency
  • The Networking API
  • Making something reliable
    • timeouts
    • recovery mechanisms
    • protocol levels where this could be done
      • TCP/IP
      • Application level
  • Ordering
    • Bare wire
    • Reordering
    • Role/use of UDP
    • How is ordering achieved,
  • Internet Structure
    • IPv6
    • network of networks
    • DNS
    • ping
    • traceroute
    • wireshark
    • ARP/MAC addresses
  • Naming/Discovery
  • Stream vs Messages
  • P2P
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2024 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback