This is the main repo for the course RES, taught at HEIG-VD in 2020.

This is where you will find lecture notes, slides and some of the examples presented in the class. We will also keep links to the different repos used throughout the semester (for assignments).

• Thursday, May 28th: deadline to submit the HTTP infrastructure lab
• Monday, June 1st: deadline to submit the HTTP infrastructure lab
• Friday, June 19th: second written test
• Sunday, June 28th, deadline to submit the Orchestra lab (UDP)

• YouTube playlist

• Here is the repo for the first assignment. Make sur to fork it, before cloning your fork on your machine.
• Here is the Youtube playlist that presents the first assignment material.

• Here are the slides
• Here are the lecture notes
• Here is the project used to present the impact of buffering on performance
• Here is the repo for the lab, which we will work on during weeks 2 and 3

• We are still using the same deck as last week
• Same thing for the lecture notes
• Here is the project used to demonstrate File IOs
• Here is the project used to demonstrate character encoding

• Here are the slides
• Here is an example of a simple TCP client (which does NOT implement the HTTP spec)
• Here is an example of a simple TCP server (streams current time)
• Here is an example of a multi-threaded TCP server (with workers)
• Here is an example of a client-server application (presence)
• Make sure that you have a working Wireshark on your machine!
• Here is the repo for the protocol design exercise

• Review of protocol design exercise, with student presentations & demonstrations
• Intro to Docker & UDP
• COVID-19 RESPONSE PLAN
• Important: please take the time to study all the lecture notes until TCP programming. Make sure that you know how to implement a client and a server (also a multi-threaded one). If you are stuck, or if there is something that you do not understand in the code examples, SHOOT OUT.
• There is still a test coming up in 2 weeks!!

• Review the protocol specification. We will look at your proposals, identify issues and walk you through our specification. As mentioned during the last lecture, be ready to write a protocol spec in an upcoming evaluation (test and/or exam).
• Focus on Docker introduction. Here our goal is to understand what Docker is and why it is a useful technology that we must all master.
• We will use videos to share knowledge and lab procedures do get familiar with the basics (installation, creation of images with docker build and launching of containers with docker run).
  • The videos are available on the RES 2020 YouTube playlist:
    • Docker (introduction)
    • Docker (architecture and installation)
    • Docker (images and containers)
• This introduction is critical for the follow-up weeks.
• The teaching team will reach out to you during the normal RES lecture and lab sessions to see how you are progressing and help you.

• We maintain the evaluation as scheduled. We still need to figure out the logistics, but everyone must be available on Teams on April 3rd, at 10:25 sharp. If for some reason you are unavailable at this time, please reach out to me BEFORE the time.
• It will cover everything until TCP programming and the Docker introduction.
• During the evaluation, you will very likely have to create and run Docker containers, based on the short procedures presented before.
• During the lab session, watch the additional Docker video: Docker (top 10 commands).

• Read the 2 chapters on HTTP protocol and Web Infrastructures, to get ready for the lab.
• Because of the Easter "break", you have 2 weeks to do that. Please do it. Please.

• We start to present the HTTP protocol, so that you can get started with the HTTP infrastructure (long) lab. We are preparing videos to present this material.
• This week, the goal is to get familiar with the basics of the HTTP protocol. After watching a series of videos and studying the lecture notes, you should be able to describe the syntax of HTTP messages (requests and responses). You should also be able to describe what are the most important status codes that HTTP servers send back to the client.
• In the videos, we show demonstrations of various tools (including servers running in Docker containers). You have to redo these experiments on your machine (but you don't have any report or deliverable to submit - it is prep work for the upcoming lab and tests).
• For the videos, watch these 4 videos in the "Le Protocole HTTP" playlist:
  • introduction
  • outils
  • observation
  • codes de status
• For the lecture notes, study this chapter:
  • Lecture 4 - HTTP
• For the slides, look at:
  • Lecture 4 - HTTP
• The teaching team will reach out to you during the normal RES lecture and lab sessions to see how you are progressing and help you.

• We continue with our presentation of HTTP in videos for the theoretical part.
• We start working on the HTTP infrastructure lab. We already have a series of 12 webcasts (~6 hours) that guide you through the process, so we are in good shape.
• In this lab, we will use Docker to create a complete web infrastructure with a reverse proxy and several HTTP servers.
• All the instructions for the HTTP infrastructure lab are available in this repo, with links to the YouTube webcasts.
• The teaching team will reach out to you during the normal RES lecture and lab sessions to see how you are progressing and help you.

• We continue with the HTTP infrastructure lab.
• The teaching team will reach out to you during the normal RES lecture and lab sessions to see how you are progressing and help you.

• We continue with the HTTP infrastructure lab.
• We maintain the date for the evaluation, which will focus on HTTP.**
• Both on the protocol aspects (presented in the new videos) and on the infrastructure aspects (presented in new videos and put in practice in the lab)

• We complete the HTTP infrastructure lab.

• We introduce UDP programming

• We start the "UDP Orchestra" lab.
• Here is the repo.

• We complete the "UDP Orchestra" lab

• Second written test.

• Sunday, March 8th: everybody must have (individually):

• completed the Java IO lab

• Friday, March 20th: everybody must be ready to do a demo of the Calculator client-server.
  • Your code must be available in a GitHub repo

• Friday, March 20th: execute the code (with the debugger and Wireshark) and study the code of the 3 examples.
• Friday, April 3rd: everybody must be online at 10:20 sharp, ready to do the first test for the semester. The scope for the test is defined as follows:
  • You must have studied all the material (lecture notes, slides and code examples) for the chapters on Java IO and TCP programming.
  • You must have watched the following videos about Docker on the RES 2020 YouTube playlist:
    • Docker (introduction)
    • Docker (architecture and installation)
    • Docker (images and containers)
    • Note: Docker (top 10 des commandes pour démarrer) has been recorded afterwards. It is useful to watch it as well (the first part, relatively short, lists the commands, the second part is a demo). The video is particularly useful to understand the difference between docker run and docker exec, two commands that are useful for analyzing containers.
  • While watching the Docker videos, you must have installed Docker and made your own experiments with the GitHub repository that shows how to package a TCP server implemented in Java into a Docker image. You must be able to start a container running the server. You must be able to start another container in interactive mode and to connect to the server with netcat.
  • Last but not least. You must be really sharp on the process to design and specify an application level protocol. You must have watched very carefully this video on the YouTube playlist. You must be able to apply this process for a new protocol.
• The test will be organized as follows:
  • At 10:15, everybody joins the channel "Travail écrit 1 (AB)" on Teams, so that at 10:20 everybody is ready to go.
  • At 10:20, I will share an invitation to an "assignment" in a GitHub classroom. You will get access to a private GitHub repository, where you will have the guidelines for 2 exercises. You will provide your solution in files, that you must not forget to commit when you are done! The system automatically creates a pull request and a feedback branch, where you will get my feedback after the grading.
  • IMPORTANT: The deadline to turn in the assignment will be set to 11:45 in the system. This means that any commit you do AFTER the deadline will be ignored by the system. So, as soon as you start to work on your solution, commit and push what you have done so far.
  • At 11:50, I will release a quiz on the "Travail écrit (AB) channel". You will have 10 minutes to answer 10 questions.