|
Definately channels should be a demand basis, within a client/server model. In IMC2's though case is that at present it (including IMC2 3.00 that Samson made) is still a peering system. Every mud has the capacity of being a hub, a system like I3 does not allow this. v3.00 has more constraints on it that no longer make this completely viable (Samson removed the capacity for multiple connections for one thing), but its still working under the networking assumption its a peering system, as most of the existing IMC2 network thinks as the bulk of them are still IMC2 v1-v2.00g implementation.
A client/server model would give you your central point of query, except with IMC2 when you distribute the channels across all the muds (muds having compiled in ICEd, the hosting side of the channels) there is technically no servers. Thus everyone is potentially a server and either everyone queries everyone else, or those few broadcast.
|