Day 17

152.33.57.228 is my IP address

I've always wanted to own a boutique and name it "Strawberry Fields" since my last name is Fields, so I looked up the domain on www.whois.com. Unfortunately, strawberryfields.com is taken by a cheese company (??) and strawberryfields.net wasn't registered because they failed to comply with whois.com regulations. I visited strawberryfields.net and found that it's a site dedicated to keeping the memory of John Lennon alive. I JUST checked out strawberryfields.com and it turns out it's a site for think-tank services, so I don't know how reliable whois.com really is.

Registrant:
Belton Cheese Limited
Belton Farm
Whitchurch, Shropshire SY13 1JD
UK

Domain Name: STRAWBERRYFIELDS.COM

Administrative Contact:
Strawberry Fields
Barbara Rainford
Prees Green
Whitchurch, Shropshire SY13 2BN
UK
01948 840102

Day 16:

I was sent the word "knCUDATE", but after discussing with my sender, I was supposed to have received "incudate". I received the binary code correctly, but the sender didn't translate ASCII into binary properly. I sent out the word "xylocarp". I could not find either of these words in an online dictionary.

With the whole class using the random method of sending/receiving, it took about an hour for me to get my 8-byte message. It took about 45 minutes for me to send my 8-byte message. I found it easier to send a message, because once you establish that it's your turn to send, all you need to do is read the numbers. When you are receiving a message, you need to record and interpret it. If you're doing this, it keeps you from sending another message until you're finished. Theoretically, you could send consecutive messages if there are no collisions, but it would be much harder to receive consecutive messages.

Some difficulties arose during the random method, because people often tried to go at the same time by blurting out the second someone else was finished. Usually more than one person had this idea, and in the lull that came after the collision, someone else could get a word in. When we tried to do sender/receiver (hot potato type approach), many people were left out of the loop and were not able to send or receive any messages.

To make the process more efficient, I would suggest moving in a circle and pausing for a moment of silence if you're finished sending. This hesitation will let the next person know they can go.

Day 15: Bus Topology

To handle the issues of addressing and communication conflicts in a Bus network, each computer would be assigned a subgroup and a number, as in the classrooms here. (by room number and computer number, i.e. 201-13) This would give a smooth method of addressing the computers. If everyone was trying to use the server at once, common requests (open firefox) can be automated so that a simple shortcut instruction is sent through the buses. These tasks would take up less room, and others would be carried out on a first-come, first-served basis.