bnls multi server support with failover

[GoogleCodeExporter]

I'd like for GHost++ to support failover bnls reconnections to other bnls
servers based on a distributed and maintained list that came with the software.

This list would have all the active bnls server definitions and could
easily be maintained.

When a bnls server goes down, the bot will lose its connection repeatedly
to battle.net should warden be active and could cause temporary bans. If
GHost++ could detect a down bnls server, it could move on to the next one
and connect to it halting the repeated connection attempts.

I think the only ghost.cfg variable that should be left and needed is maybe
the cookie number for each bnet_connection subset.

Thanks for this great bot and any discussion over this issue would be
appreciated.

Original issue reported on code.google.com by robertcl...@gmail.com on 7 Sep 2009 at 3:30

[GoogleCodeExporter]

I don't like the idea of including a static list of BNLS servers with GHost++ 
and I
don't like the idea of running some kind of "master server" which maintains a 
list of
BNLS servers. Aside from that, there's round robin DNS (as mentioned on the 
forums)
and the possibility of specifying multiple BNLS servers per connection with the
intention of rotating through them. I don't mind that idea, especially because 
it
would be backwards compatible. I'll consider this issue accepted for now, but 
low
priority.

Original comment by hogantp on 14 Sep 2009 at 6:32

• Changed state: Accepted
• Added labels: Priority-Low, Type-Enhancement
• Removed labels: Priority-Medium, Type-Defect

[GoogleCodeExporter]

well you could add in your config
bnls_updatelist = site that host a list of bnls servers (I might help with this)
and have bnls.txt with the different bnls servers pulled so you can add yours 
own to
that text

Original comment by Absolute...@gmail.com on 21 Sep 2009 at 8:34