I have two potential topologies which could be implemented for the system.
In the first scenario, every node has it's own direct connection to the Internet which is used to get to the profile server. In this case each node is responsible for it's own bandwidth.
The second kind of network is based on that of a mesh network. In this system some nodes have no direct connection to the Internet. Nodes are either connected only to other nodes, or other nodes and the Internet.
In this system the network is more robust. If the connection to the Internet for the node you are seated at goes down the node would still be able to reach the profile server through another set of node. Also, those nodes which are on the Internet would generate more bandwidth because the requests have to go through them. These points would act as a bottleneck for the entire system, and would cause it to become slow.
To ensure each node is given a fighting chance I have decided to start off using the first topology. After a period of time traffic reports for each node would be generated, and those not using much bandwidth could be merged to share an Internet connection.
Also, while it had been my initial intention to give the nodes a wireless Internet connection, my research has indicated this might not be such a good idea. High activity on a wireless Internet connection has detrimental effects on bluetooth connectivity. Because of this only a few nodes would have wireless Internet connection, those which needed them like Internet café nodes. The rest of the nodes should be given wired Internet connections. Due to the location of the nodes, built up areas surrounded by businesses or in the suburbs, access to an Internet connection should not be a problem.
Here is my neat and final representation of the network topology:
