Connection Balancing
It is not uncommon to find the same AKA Name registered one or more times locally, and one or more times remotely. If a Name Server has the same AKA Name registered more than once, connection balancing occurs between the registrations, whether or not they are local or remote registrations. It is possible to skew the connection load between machines participating in a server farm if, for example, one of the machines is more or less powerful than the others. Do this by increasing or decreasing the number of registrations that point to that machine.
For connection balancing to work, the supplied client OpenROAD Name Server components must be used to make a connection:
• For OpenROAD clients, this means that ASONameServer must be used to make the connection.
• For non-OpenROAD clients, the Connect method of either the OpenROAD.RemoteServer class or the OpenROAD.ASOSession class must be used.
If a hard coded connection signature is specified using the Initiate method, this overrides the Name Server connection process, and connection balancing does not occur.
An OpenROAD Name Server node in the tree view appears for each local or remote Name Server that is successfully accessed:
