Day 15- Bus Typology

I think the best way to solve the communication issue in a bus typology could work similarly to how I think e-mail works with sort of mini servers. For example, your message could get sent to whatever server is at the end of your bus and then ask the question is Aunt Mary's computer on the same bus and then if not, which is hers. E-mail (I think) does this where I send an e-mail to gmail and it passes it on to yahoo mail which delivers it to auntmary@yahoo.com. Or, it could use something like the IP address of a computer so that when I say to send it to Aunt Mary, my computer puts the IP address of Aunt Mary's computer coded into there somewhere. So then, it follows around the bus (linearly?) until it gets to Aunt Mary's computer or back to mine with an error.

To solve the issue of communication, the bus could have several wires to handle different types of information. So, for the 30 computers in this room, each funciton of the computers is broken down and uses a different wire. Or, it could work like a CPU- instead of "multitasking" it just shifts really quickly between all the different tasks. The first would mean the bus would need to be physically large, containing many wires, but it would probably be faster than the second since it would only depend on say 30 instant messaging conversations per wire rather than 30 conversations, emails, radios, and online purchases all at once.