We all know the concepts of clients, hubs, and the server that they register to. I'm suggesting a higher level in the "hierarchy", namely a hublist-list server. It could look something like this; on a standard xml on a http server (sourceforge, for instance)
Code: Select all
<Hublists lastupdated="2003-04-23">
<Hublist url="http://ahublist.com/hublist.config" format="DC1">Hublist name here</Hublist>
<Hublist url="http://ahublist.com/hublist.config" format="bz2">Hublist name here</Hublist>
</Hublists>
The format tag?? Because DC++ only recognizes bz2 lists if there is a .bz2 extension. That means, trying to use querystrings on a php page won't work, unless you make a &x=.bz2 dummy variable come last. And it can be quite handy.
This page could be slimmed down too, I guess. Instead of <Hublist> just <HL> and so on. If the bandwidth is an issue that is.
Hmm, a value should also be included to set all clients to change to a different hublist-list, if the server is about to go to eternal sleep or if the bandwidth requirements can not be met. Or, several mirrors of the list could be hosted and the all the URLs included in dc++, but randomly select one when grabbing it to even out.
Well.. should be one thing or another to discuss here now. Hope you like my idea.