-
Notifications
You must be signed in to change notification settings - Fork 6
Exercise9StandardizeEscapeRoom
Assigned | 9/30/2019 |
Due | 10/2/2019 |
Points | 25 |
This assignment should require almost no code writing. You should be able to reuse your code from exercise 7 almost without modification. All that is required is that your Escape Room clients and servers are compatible with everyone else's clients and servers. For the most part, the only change should be "standardizing" the packets across the class.
The only changes to the code are the following:
- You will NO LONGER transmit your packet definitions. The autograder start test packet no longer has a
packet_file
field.
The PETF needs to upload to slack a PRFC (to channel #labs_and_exercises
, please pin it!). The PRFC can pretty much copy the protocol right out of the exercise 7, removing the autograder pieces. That is, it should describe an escape room client and escape room server connecting and interacting.
It MUST include all the finalized packet definitions agreed on by the PETF. This only needs to include the DEFINITION_IDENTIFIER
, DEFINITION_VERSION
and FIELDS
. You do not have to include the factory functions in the PRFC. Technically, they are not required for interoperability (although I recommend you still use them so the rest of the code remains unaltered).
There is technically no due date on this, but as you can't finish the assignment without it, I hope you submit it soon.
Once I have the PRFC, I will set up an autograder. Again, everything should work exactly like in exercise 7. All we're doing here is standardizing our packets.
As usual: 20194.0.0.19000 and port 19008
Some will notice this is named exercise 9. That's because I cancelled one exercise. So it's technically exercise 8 but I'm not renaming the page.