Team 8 Protocol Reviews
-----------------------

Chaudhuri.pdf [2]
Inadequate specification does not cover the various scenarios covered in the class discussions.


Reza.pdf [2]
Too verbose. Chatroom maintenance not covered.
This specification states that ?Switching Servers: An client simply sends a client_connect request to another server from the list of known neighbors?
Do all the user agents of a failed server migrate to one server? If not, who owns the chatroom when the server fails? How does A and B (in the same chatroom) continue to communicate if their server failed and they migrated to different servers?


Team01.pdf[3]
Failure detection and recovery not explained well. Chatroom maintenance not covered.
Do all the user agents of a failed server migrate to one server? If not, who owns the chatroom when the server fails? How does A and B (in the same chatroom) continue to communicate if their server failed and they migrated to different servers?


Team02.pdf [4]
Simple and good specification. However chatroom maintenance is not covered. Who owns the chatroom when the server fails?


Team03 [Score=2.5]
Protocol is not complete and not clear, does not cover all cases of communication. chatroom ownership is not covered.


Team04 [Score=2.5]
Team concentrates on the easy part of the communication, but touches little on the more important stuff
Server recovery not describe, children recovery not discussed, chatroom ownership not described.


Team05 [Score=2.5]
Name collision not discussed in server discovery. Chatroom ownership not covered. no details are given, just general description instead.


Team07 [Score=3.5]
Good. protocol described is workable. chatroom ownership not discussed.


Team09.pdf [2.5]
Not sure if using a directory service is ok for this project, what if the the directory server fails? Doesn't specify the exact messages, only message types and codes? Doesn't discuss chatroom ownership at all.


Team10.pdf [4]
Good, simple messages, easy to understand. Doesn't discuss chatroom ownership. What happens to a chatroom when the server goes down?


Team11.pdf [3.5]
Implements good load balancing technique and covers most cases of the server failure but Chatroom ownership is not handled properly.


Team12.pdf [3.5]
Good server discovery protocol. Commands are simple and explained clearly. Chatroom ownership is not handled properly in case of server failure and recovery. If user agenst of a failed server are in a chat room and migrate to to different backup servers, how they will participate in chatroom communication.


Team13.pdf [3]
Simple and clear message formats. Chatroom ownership is not handled properly in case of server failure and recovery.


Team15.pdf [2.5]
Covers most cases like server discovery and neighbor selection. Command are not very clear. Also if user agenst of a failed server are in a chat room and migrate to to different backup servers, how they will participate in chatroom communication.