You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 21, 2021. It is now read-only.
Due to irregular scheduling across the semester, there was a break of three weeks from the previous lecture to this session. I hadn't announced that we'd be doing the second debugging exercise, so students were not prepared. As most of them are not developing in Java on a regular basis, they had a cold start. My mistake, I should have announced it a week in advance.
I fell for #117 again. I thought there was no client IP check for JRMI, but I actually implemented it in 2019 (#91#92).
Timeline:
10 min introduction to the exercise and looking up stubs in a catalog
7 min introduction to APIs, of the exercise and of Java RMI in general
16 min self-paced debugging
9 min demonstration how to fix the first problem (registry lookup)
13 min self-paced debugging
18 min break, while demonstrating how to disable the client IP check
10 min "Eight Fallacies of Distributed Computing" (unplanned)
and demonstration how to fix the second problem (lookup ticket issuer)
10 min server code walkthrough: creating, exporting, registering the remotely callable objects
and feedback gathering
The text was updated successfully, but these errors were encountered:
Please provide your feedback in the comments.
Due to irregular scheduling across the semester, there was a break of three weeks from the previous lecture to this session. I hadn't announced that we'd be doing the second debugging exercise, so students were not prepared. As most of them are not developing in Java on a regular basis, they had a cold start. My mistake, I should have announced it a week in advance.
I fell for #117 again. I thought there was no client IP check for JRMI, but I actually implemented it in 2019 (#91 #92).
Timeline:
and demonstration how to fix the second problem (lookup ticket issuer)
and feedback gathering
The text was updated successfully, but these errors were encountered: