You have 5 machines, each connected to the internet.
Each of these machines is hooked to the main server.
Each machine can handle let's say a maximum of 200
Users. That means 1000 users connecting to 5 machines
throughout the network. These 5 machines transmit
respective data in real-time to the main hub server.
Each machine transmits it's own set of chat messages
and file catalogues. The central server then transmits
recieved data from each machine to the others, making
a complete cluster, so each machine has a complete
network snapshot from chat, users and network data and
addresses.
When a user requests files or chat, the machine he is
connected to has all the required information needed
for communication, thus the user can bypass the
network as long as there is no lag in the address
information.
I understand this may not be as easy to code as it is
to plan, but maybe clustering is in the future. If
developed, it would certianly accelerate the growth of
the DC Protocall.
Logged In: NO
I think it would be one of the greatest things that could
append to the DC community.
Logged In: YES
user_id=456215
i've written a protocol to manage Clustering Servers :)
i'm writing my own dc hub server...but i've uploaded my docs
on Multi Hub! This is simply to do :)
Every time a server recive a command from a client search
the destinatary, check the HUB_Provenience and send the
command to HUB or to the client (depends of
HUB_Provenience variable) and other things...i'm very happy
to collaborate with opendcd if the master developers want!
this is the link of my project ->
http://sourceforge.net/projects/odchub go in doc section and
get the file called "DC protocol MultiHUB written by
daniele_dll.txt" in english section :)))
byz
Logged In: YES
user_id=456215
infact! I've writed this simply sistem for this reason! hovewer
i've email all that are writing dc hub servers! If we make a
unique link system the users will be more happy! So a user
will use the Hub Server that prefer!!!
:P
byz and tnx