The Internet is a large and complex collection of machines. Learning Internet protocols and network characteristics is a challenge for students in part due to the diversity of Internet devices. Seattle makes learning about the Internet easy by providing students with a simple to learn Python-based language and a tool-rich environment that simplifies distributed deployment and monitoring of programs running across Internet hosts. Seattle can help instructors augment lectures with real-world, hands-on assignments across thousands of computers. As of May 2010, Seattle has been used in 11 classes at universities around the world. The Seattle team is dedicated to helping instructors get started with using Seattle in the classroom.
+The Internet is a large and complex collection of machines. Learning Internet protocols and network characteristics is a challenge for students in part due to the diversity of Internet devices. Seattle makes learning about the Internet easy by providing students with a simple to learn Python-based language and a tool-rich environment that simplifies distributed deployment and monitoring of programs running across Internet hosts. Seattle can help instructors augment lectures with real-world, hands-on assignments across thousands of computers. Seattle has been used in dozens of classes at universities around the world. The Seattle team is dedicated to helping instructors get started with using Seattle in the classroom.
Quick Links
Battle-tested Programming Assignments
+
Battle-tested Programming Assignments
-
Networking / Distributed Systems
- The first take-home assignment (no programming required!)
- A Stop and Wait protocol
- A Sliding Window protocol
- Introduction to Link State Routing
- Web Server
- Chat Server
- Distributed Hash Table
+ The first take-home assignment (no programming required!)
+ A Stop and Wait protocol
+ A Sliding Window protocol
+ Introduction to Link State Routing
+ Web Server
+ Chat Server
+ Distributed Hash Table
Security
- Building a reference monitor
- Attacking a reference monitor
+ Building a reference monitor
+ Attacking a reference monitor
Operating Systems (on the way!)
More assignment and project ideas
+More assignment and project ideas
FAQ
diff --git a/index.html b/index.html index 00fd0be..db45f4e 100644 --- a/index.html +++ b/index.html @@ -75,8 +75,8 @@Detailed information on the project is maintained on the Seattle Wiki.
+Detailed information on the project is maintained on the Seattle docs repository.
Quick Links
FAQ
@@ -43,7 +43,7 @@ A: Our intent from the outset has been to maximize security. We believe our system is safer than existing code sandboxes for web applications that are prevalent on all systems. However, any software adds risk. Q: What sort of network traffic will my computer send?
- A: By default, Seattle only allows a user to listen on TCP and UDP using local ports 63100 - 63199 (inclusive). Outgoing traffic will use ports greater than 1024. There is an optional module under development that will restrict the source and / or destination of Seattle traffic to only other Seattle nodes.
Q: What files are accessible by programs running in the Seattle virtual machines?
A: Programs running on Seattle are restricted to reading and writing files in a single directory that is below the Seattle installation directory.
Quick Links
Q: What are the restrictions on how I use Seattle?
- A: See our Acceptable Use Policy.
Q: What is Seattle Clearinghouse and how does it differ from Seattle?
A: Seattle is the core software that all end-machines run. Seattle Clearinghouse is a communal website that allows users to pool and share Seattle resources. Resources that are allocated to Seattle Clearinghouse result in the researcher ceding direct control over the donated resources.