Commit 427e385d authored by Taddeüs Kroes's avatar Taddeüs Kroes

Telematica ass1: Fixed typo's.

parent d870a0f3
...@@ -50,9 +50,8 @@ Protocol specification ...@@ -50,9 +50,8 @@ Protocol specification
---------------------- ----------------------
The instructions of this assignment required that the client and server should The instructions of this assignment required that the client and server should
communication according to a given protocol. The protocol [4]_ is not further communicate according to a given protocol. Because the protocol [4]_ is already
discussed in this report, since the protocol is described clearly and it would described clearly, we did not add it to this report.
be redundant to add it to the report.
.. [4] Client / server protocol: .. [4] Client / server protocol:
http://staff.science.uva.nl/~mlankamp/2011/Telematica/protocol.desc http://staff.science.uva.nl/~mlankamp/2011/Telematica/protocol.desc
......
...@@ -207,10 +207,10 @@ In order to create a list of currently active users, we used an dictionary based ...@@ -207,10 +207,10 @@ In order to create a list of currently active users, we used an dictionary based
on the client's address tuple (ip address, port). To check if a user does not on the client's address tuple (ip address, port). To check if a user does not
take the nickname of an existing user, we simply iterate over the list of active take the nickname of an existing user, we simply iterate over the list of active
users and compare the name of each user with the requested nickname. If it users and compare the name of each user with the requested nickname. If it
exists, return a negative response, otherwise if the nickname is valid according exists, return a negative response. Otherwise, if the nickname is valid according
to the protocol, return a positive response. It is possible to build an index to the protocol, return a positive response. It is possible to build an index
for the name lookup, but that optimization is not worth it as long as there for the name lookup, but that optimization is not worth it as long as there
aren't many clients connected. And if there are many clients connected, there aren't that many clients connected. And if there are many clients connected, there
are more important scalability problems to solve (e.g. better socket are more important scalability problems to solve (e.g. better socket
multiplexing, synchronisation between different server and load balancing). multiplexing, synchronisation between different server and load balancing).
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment