Distributed Systems 2016 Grades
 Share
The version of the browser you are using is no longer supported. Please upgrade to a supported browser.Dismiss

 
View only
 
 
ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAIAJAKALAMANAOAPAQARASATAUAVAWAXAYAZBABBBCBDBE
1
Student IDFinal Grade (rounded)Final GradeAssignment 1Assignment 2Assignment 3Assignment 4Assignment 51.11.22.12.22.33.13.23.33.43.5
4.1/4.3(en)
4.2/4.1(en)
4.3/4.2(en)
4.45.15.25.35.4Sum pointsFraction not GermanSum points w/ languageExam gradePoints for 30:CommentTotal points98
2
GradeCommentGradeCommentGradeCommentGradeCommentGradeComment7541010644564734348490
Total points (old)
61
3
5279771Wrong answer, no explanation3used service not described, only protocol named000600061300100021217
4
74621717.142857144right answer, but chaotic explanation. you say because it is connectionless, but then discuss extensively TCP? connectionless nevertheless would apply to IP under TCP, but that is not mentioned..43adaptive treewalk is a hybrid protocol4situations are right, but explanation is missing5.5802.11 is wifi4.5C wrong1It is a routing strategy! Routers know not every address, but group them hierarchically1Scalability is an issue, but what concretely? Size, and keeping it up-to-date50---------323217.14285714
5
76042625.8949152530
Please submit only once in the future
30
Please submit only once in the future
3030
MirisWonderfulMagicMD5Cracker
30see 121815correct, but a bit short. what is the differentiation to the phone network?3service used missing, UDP is just the protocol45situations are right, but without proper explanation04.5C wrong43.55642port einigen wie? IP woher?34147lookup in chord?4696923
6
877477.1666666670your answer describes the technology not the concept2.5used service wrong45situations are right, but without proper explanation0000000334000021.521.57.166666667
7
103331818.166666675slight contradictions, is it connectionless or not?2.5which service of UDP is used?45situations are right, but without proper explanation04.5C wrong33.5564314040054.554.518.16666667
8
103701817.833333336044situations are right, but explanation is missing24.5C wrong00561304148153.553.517.83333333
9
105182020.48884181029
Nice documentation. The discussion of UDP misses the core a bit however, for instance that with UDP, it becomes a challenge to know who is actually connected
26further improvements to deal with multiple clients would be needed. For instance, storing a list/set of clients, instead of a single one.4"switching" also happens in the mail network!3service used missing, UDP is just the protocol4724.5C wrong2.505317340450595919.66666667
10
114393030
Very nice documentation and testing
30
comparison TCP-implementation: interesting argument about security.
30
Trattore con motore: 2nd place in lab A
29----#VALUE!#VALUE!#VALUE!
11
116122323.25898305300plagiarism28
nice solution, but documentation would benefit from more structure, and discussion difference TCP/RMI implemention could be more abstract.
30296good for pointing out connections to both, but what about packet switching?3used service could be described more crisp41090005346name services?31unlikely problem, compute power would run out first before sockets run out246268161.220.4
12
121812322.9389830530
Please submit only once in the future
30
Please submit only once in the future
3030
MirisWonderfulMagicMD5Cracker
30Cool strategy, scouts avoiding each other, fighters around anthill, ...73service used missing, UDP is just the protocol4100021563034044lookups how?1575719
13
122192525.4022598930
Nice space efficient solution
30
Very nice testing and nice UDP discussion
30
Nice documentation. Comparison with TCP: The argument with more overhead of RMI is a generic argument, but in case of this chat application I would like to hear in more detail whether this is an issue.
30
MirisWonderfulMagicMD5Cracker
3073service used missing, UDP is just the protocol44situations are right, but explanation is missing5good argument with duplex, but explanation of csma/cd is basically missing031563.5TCP slower relevant for chat?2port, IP from where?342.5482676722.33333333
14
122372827.865536723030
Nice UDP discussion
3030Der Gerät3073service used missing, UDP is just the protocol4105good argument with duplex, but explanation of csma/cd is basically missing3B, C wrong33.5563.5TCP slower relevant for chat?42each one thread and one socket4interesting alternative to concurrency33super-peer is a special case of unstructured62777725.66666667
15
122433029.8361581930
Nice documentation
30
+ For thinking of international support and for correctly acknowledging ideas from others
30see 1250931
1st place in the competition lab A
295.5mail system is also distributed. important point is packet instead of circuit-switching, thus similarity to mail system is probably higher3service used missing, UDP is just the protocol4109collision detection?4.5B wrong33.556431.5threats?4interesting alternative to concurrency3484858528.33333333
Could hardly read everything. Please write clearer
16
1225130See 1225130
Nice idea of using UDP broadcasts to discover servers! No problem that it is a single file
30see 1221930MD5nack30see 12219----#VALUE!#VALUE!#VALUE!
17
122862221.71644068030See 1143930See 1143930
Trattore con motore: 2nd place in lab A
30Superants7! very good, pointing out similarities to both!3service used missing, UDP is just the protocol45situations are right, but without proper explanation6binary exponential backoff?0400632and how to get IP and port?301.5what does "organize" mean?48460.5154.4518.15
18
123042221.813559323030See 127153030haribo13service used missing, UDP is just the protocol47situations are right, but high load situation without proper explanation9collision detection?4.5C wrong415641.5ports? and how to get IPs and port?001420575719
19
1230676.7529See above13service used missing, UDP is just the protocol3token?103A, C wrong20.5504good argument about length000000022.5120.256.75
20
124172928.7118644130
Nice method introduceErrors()
30
Very good and concise discussion of the UDP case
30
for concisely mentioning the key advantage of RMI: Transparency
31
1st place in the competition lab A
30Very nice documentation73service used missing, UDP is just the protocol4106binary exponential backoff?63.53.5463.5does speed matter?6name services?322.5460808026.66666667
21
124211515.1666666730
+ that you investigate also limitations
0plagiarism30
very well-written documentation, and nice features (whisper, chatrooms).
30haribo30Nice documentation7Nice other similarities, besides switching!2.5service used missing, and TCP is generally seldomly used3tree walk is hybrid3.5situations are somewhat right, but explanation is missing003.53.55341.5ports? and how to get IPs and port?31230045.545.515.16666667
22
124611413.830
Nice documentation
29See above30frititati72.5service used is missing43.50csma/cd?003.5563.5does speed matter?3hardcoding? name services?34interesting alternatives to synchronization problems000046141.413.8
23
125001010.27333333029
Nice documentation. -1 for late submission.
30frititati12.5service used is missing44003.535630001.500033.50.830.8210.27333333
Could hardly read everything. Please write clearer.
24
125022727.1265536730
Very good documentation
30Nice discussion30
Nice documentation, weird login-logout-bug
30see 1251730Nice coordinate calculation and communication04host-to-host is network layer46situations are right, but high load situation without proper explanation9collision detection?632.5563.5does speed matter?70threads..4Good alternative to concurrency346how do lookups work?1747424.66666667
25
125092221.9536723230
Nice documentation
30See 1224330
interesting dummy method for checking whether clients are still up, though I am wondering how well that would work over a long-distance/unreliable (e.g. mobile) connection? Das Deutsch ist sehr gut.
31
1st place in the competition lab A
2973service used is missing45situations are right, but without proper explanation04.5B wrong00563.53and how to get IP and port?30.51.5430535317.66666667
26
125172423.9735593230
Very good documentation
30See 1250230see 1250230
Interesting general discussion
30See 1250203service used missing, UDP is just the protocol46.5situations are right, but explanation limited9collision detection?3B and C wrong44564600no loop for RMI needed for accepting connections2.5470you describe instances, not application scenarios68161.220.4
27
125292828.0671186429
Nice solution, separate documentation would improve readability
0plagiarism30see 1242130haribo30Interesting airing of continuous signals74Right service from below, but service provision explained the wrong way around47.5why token ring not good for low?9collision detection?4.5C wrong43.55646name services?343472.588179.226.4
28
125373030.2602401130
Nice error output
30
Very nice discussion of complexity and of issues with multiple threads! Discussion of UDP misses the core however a bit, how to manage connections.
29
Documentation a bit short. Observation with version check of RMI interesting, but does it really work? RMI only cares about the interfaces, not how they are implemented?
31
1st place in the competition lab A
30See 12417754106binary exponential backoff?4.5B wrong43.5563.5does speed matter?733347186.586.528.83333333
29
125552827.898305083030
Nice testing and UDP discussion
30
nice documentation and testing
30Der Gerät28Late submission73service used missing, UDP is just the protocol46.5situations are right, but explanation limited5good argument with duplex, but explanation of csma/cd is basically missing3B and E wrong43.55644name services?342464787826
30
1259030See 1260430See 1260430frititati29see 12604----#VALUE!#VALUE!#VALUE!
31
125942929.3583333330
Good documentation, nice console program
3030
nice solution, but documentation would benefit from a bit more structure.
30MD5nack297546.5situations are right, but explanation limited9.53A, E wrong44563.5does speed matter?4name services?34148283.583.527.83333333
32
126041616.4066666730
Very good documentation
30
Interesting point that UDP server would actually get simpler in that it would not need threads anymore
30frititati29Who is the "I" that wrote the report?5
TCP is connection oriented, but the IP protocol below, is not!
3service used missing, UDP is just the protocol46.5situations are right, but explanation limited13
B, C wrong
445643and how to get IP and port?32000053.50.849.2216.40666667
33
126813029.5898305130
Nice documentation
3030
Nice documentation. Though I am wondering why for RMI you had to open ports, and for TCP not?
30
Trattore con motore: 2nd place in lab A
30Superants73service used missing, UDP is just the protocol410104.5B wrong43.55646how can the port be known?3answer contained in (iv)0answers (iii), not (iv)347how do lookups in Chord work?848428
34
1268729
Nice solution, separate documentation would improve readability
0plagiarism30
MirisWonderfulMagicMD5Cracker
30----#VALUE!#VALUE!#VALUE!
35
126892727.177824863029
The discussion of UDP misses the core a bit, for instance that with UDP, it becomes a challenge to know who is actually connected
29
nice implementation, but explanation of the functionality is a bit short, and would benefit from more structure
29
Documentation a bit sparse
2973service used missing, UDP is just the protocol47situations are right, but low load situation without proper explanation8collision detection?3B, E wrong3.505643and how to get IP and port?34248175.575.525.16666667
36
127152525.393220343030
+ for the lesson learned :)
3030haribo5Post office and internet generally don't send via a route that they know to the destination, but just to the next closer point..3service used missing, UDP is just the protocol45situations are right, but without proper explanation104.5B wrong40563.5does speed matter?2name services? ports?34348478170.223.4
37
101107272827.9395480230
Good documentation
0plagiarism30
nice documentation, especially the diagram. Good referencing.
30
K-Team: 3rd place in the competition lab A
30Very nice documentation on cooperation73service used missing, UDP is just the protocol4109.5collision detection how is it useful?4.5B wrong43.5561does speed and weight matter for a chat?3name services? defaults?34146how to do lookups?078.578.526.16666667
38
Average all21.77419355000
39
Average passing
25.30434783000
40
000
41
000
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
Loading...
 
 
 
Summer exam
Autumn exam
Winter exam
 
 
Main menu