Tom,
I don't think there is anything particularly wrong with your suggestion,
just that it does not meet the original remit, which was to be able to
ignore players who were not following the "rules", either intentionally or
through ignorance.
We already almost have what you propose with ports 5000/5002. Which reminds
me: IIRC 5001 is reserved for telnet. We rarely use 5002 for development
nowadays, so I suppose there is nothing stopping a bunch of like-minded guys
using that. However, I just have a final reservation - MP was meant to be
the global picture of the airspace - not just a part.
That said perhaps we do need a ban/kick/ignore like IRC for MP. We have
stepped around this issue in the past.
Vivian
-----Original Message-----
From: Tom P [mailto:zomm...@gmail.com]
Sent: 15 November 2009 20:32
To: vivian.mea...@lineone.net; FlightGear developers discussions
Subject: Re: [Flightgear-devel] Ignoring MP pilots
Hi Vivian
I think that a majority of users configures MP through a launcher interface,
so the convention would be enforced through the UI.
The launcher (fgrun or other) would show a drop-down menu with the Groups
(their name) that a user can join.
The port numbers that I showed were an example, I showed 5000-5005 to keep
backward compatibility with the current setup (5000 = beginners seems like a
good default group for the current installed base), but any consecutive
range of 5 or 10 available ports will do.
About non-complying users, I don't think it would be a great problem.
By choosing a particular group, they choose to comply with the intent of the
group, and we can write down such intent explicitly in a UI text box based
on the selected group, if you feel like.
An example:
Beginners
Welcome to FG. This group allows you to get familiar with FG and learn
from fellow pilots.
Under Air Traffic Control
In this group, pilots fly under Air Traffic Control. By joining, you
are required to comply with ATC rules, please see the details at
http://wiki.flightgear.org/. <http://wiki.flightgear.org/> ..
Fighters on a mission
This group is dedicated to flying military aircrafts, simulating
missions and dogfights.
Tom
On Sat, Nov 14, 2009 at 1:56 PM, Vivian Meazza <vivian.mea...@lineone.net>
wrote:
Pete Morgan
> Tom P wrote:
> > Hi Torsten
> >
> > That's an interesting concept, I was thinking about groups as well.
> >
> > But instead of writing extra code on top of the current client and
> server,
> > could we use different ports on the server?
> >
> > Let me explain: if I understand correctly, the server already allows
> > connection to port 5002 for testing.,
> > What if we extend the concept to multiple ports and maybe assign a
> > name to the port to make things clear.
> >
> > As you said, some of the predefined groups could be:
> > - Beginner => port 5000
> > - Adheres to/provides ATC => port 5001
> > - Combat/Fighter on a mission => port 5002
> > - Airliner => port 5003
> >
> > (I'd group "Adheres to/provides ATC" and "Airliner" together for now).
> >
> > Obviously the server will need to do a bit more work, but at least the
> > demultiplexing between groups is done by the TCP/IP stack, which is
> > quite optimal.
> >
> > The only drawback is that groups are *really* separate, it would not
> > be easy to see traffic from other groups.
> >
> > Just an idea,
> >
> > Tom
> I like this idea a lot :-)
>
Nice theory - in practice how do you ensure that users both know about, and,
more importantly, observe the convention? And, what do you do if they don't?
IIRC 5001 is used for telnet, but 5002 is rarely used for development. I
suppose that some "serious" users could use that port by mutual agreement,
accepting that some less serious players might try to join in as well.
The client side ignore device seem to have more practical merit to me.
Vivian
----------------------------------------------------------------------------
--
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus
on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Flightgear-devel mailing list
Flightgear-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/flightgear-devel
