On Fri, Mar 12, 2010 at 9:37 PM, cflrich <cflrich at cfl.rr.com> wrote:
> All,
> After some reading, this is the architecture I'm leaning towards.  The
> server will run a Murmur instance, with separate channels for the
> teams.  When the player selects a team, the server will automatically
> reconfigure the access list to allow that player to enter the team
> channel, via Ice.  This is all server side.  On the client side, when
> the player selects a team, the (netrek) client would launch Mumble via
> command line, causing it to auto connect to Murmur in the proper channel.


> Once connected, team changes can probably be handled by the server,
> moving the player automatically.
> A few questions to be answered are these.
> - Will we require folks to pre-register with the Murmur server?  I'd
> rather not, honestly.
> - How will we allow access?  I'm thinking when a player joins a game,
> the server will update Murmur's user list with the players name and a
> generated password, that is passed to the (netrek) client, which the
> client then uses to generate the Mumble session.

I'm not keen on registering but would if it was essential. So if a
session was setup for a netrek game how do we make sure outsiders
could not intrude and make mischief? When I used team speak on
Leftovers anyone could connect if they knew a few pieces of info.

> Obviously we'll need a little client support once this gets hashed out
> all the way, if we want to implement this so that it is automatic  Are
> all of the current client projects open projects?

All are except Paradise 2000 which hasn't been under active
development in years.