I don't think the MP servers have to change their philosophy. I don't think both networks should be merged: it would be better to have the possibility to choose. All this is a personal opinion, but I think your MP should remain intact, with the same philosophy, and just add into IVAO the ability to accept FG connections. You can't lose your identity, you should just gain the possibility to connect your simulator to the network of your choice based on which philosophy best suits you.
Regards, Pep. ----- Original Message ----- From: Rob Shearman, Jr. To: FlightGear developers discussions Sent: Tuesday, November 11, 2008 9:19 PM Subject: Re: [Flightgear-devel] FlightGear in IVAO network I know I am usually just a lurker on this list, and when I do poke my head in, it doesn't always make sense :) However there is one concern I have about IVAO/FG-MP interoperability which I have not seen addressed, and it goes back to a debate about MP we've had in our forum several times over now. The goal of IVAO is to provide a virtual air-traffic environment with a high degree of realism. But I don't agree that FG-MP shares that goal. It seems that a large number (often, the majority) of FG-MP users are on the network to mess around and socialize rather than participate in a multi-aircraft scenario with any degree of realism. Are we then going to revert to our idea of having separate MP networks for "serious" versus "social" sim-flying? Or are we to restrict access to our MP network only to those who desire realistic interaction? This may be a can of worms, but it's one that I would at least feel comfortable knowing had already been digested before we bog ourselves down with the technical details... Cheers, -R. Robert M. Shearman, Jr. Transit Operations Supervisor, University of Maryland Department of Transportation also known as [EMAIL PROTECTED] From: Matthew Tippett <[EMAIL PROTECTED]> To: FlightGear developers discussions <[email protected]> Sent: Tuesday, November 11, 2008 7:34:12 AM Subject: Re: [Flightgear-devel] FlightGear in IVAO network Note the subtle suggestion of the discussion here. To avoid exposing/causing concern with the GPL, keeping it completely internal and not distributing it from IVAO seems like a good idea. However, this appears to need FG to expand/revise it's MP interface to allow secure connection of external MP-FS networks. This in effect opens the FG to have other networks (that talk FG-MP) to connect. Note that in this model, IVAO would bridge it's network into FG-MP, and not the other way around. This distinction is critical for the following reason... Assuming a secure connection (public key), we have the following trusts. 1) FG will allow IVAO MP information when a IVAO network connector joins the FG-MP network. 2) By connecting, the IVAO network agrees to receive FG MP information. 3) The public key of the IVAO network is trusted by FG-MP. 4) The FG-MP network has the trust 'power' to deny IVAO if there are any problems by removing the trust of the public key. Note that the primary factor in this FG-MP is master, IVAO is slave is driven by the closed protocols on the IVAO network. It makes a lot more sense for IVAO to create a connector that talks FG-MP, than the FG jump through a larger (and to some a lot less palletable) set of hoops to have FG-MP create a connector to connect as a slave to the IVAO network. (The Master/Slave term sounds wrong and would most likely cause IVAO issues. Truster/trustee sounds more peerish, but doesn't sound architecturally right either. I suggest the two groups settle on terminology ASAP to ensure a common frame of mind.) Regards... Matthew On 11/11/08, Arnt Karlsen <[EMAIL PROTECTED]> wrote: > On Tue, 11 Nov 2008 09:31:34 +0300, Pep wrote in message > <[EMAIL PROTECTED]>: > >> The way IVAO has worked so far, as Curt says, is completely plugin >> based, in regard of flight simulators, due to the fact that the >> simulators that log in are not open source (let's change that!). In >> the case of FG, where FG itself is open source, and the MP server is >> too, there are two approaches, as Matthew pointed out: >> >> One would be FlightGear acting as a IVAO client and connecting >> directly to IVAO FSD servers. Honestly it was my first though. >> However, that would be a bit difficult both for FG and IVAO. The other >> approach, bridging both networks seems to me now better. However, I >> leave it to you guys to decide which of the two you prefer, though I >> assume you go for the second one. >> >> In case of the second one, we at IVAO could set up a MP server (or >> more), connected itself to the IVAO FSD servers. > > ..and if you modify your MP server, and, _keep_ it _in-house_, you > are not distributing etc it and therefore you not violating any GPL > or any copyrights. I believe this is a valid work-around. > >> And here, as Martin >> says, starts the religious war. > > ..nope, it is no longer necessary. ;o) > >> As I understand, a server-server >> protocol should be implemented. > > ..yes, and by your guys, Pep. ;o) > >> The authentication stuff, moreover, perhaps will demand a few changes >> to MP? > > ..maybe. Then you propose a patch or something, if it goes into FG > or FG MP servers, it's subject to copyright and to the GPL. ;o) > >> Once we start agreeing, there will be more things like these >> to address, I assume. > > .. ;o) > >> If you confirm this is the way you wish to proceed, please tell me. >> I'll report to my IVAO "bosses" and see what they decide. > > > > -- > ..med vennlig hilsen = with Kind Regards from Arnt... ;o) > ...with a number of polar bear hunters in his ancestry... > Scenarios always come in sets of three: > best case, worst case, and just in case. > > ------------------------------------------------------------------------- > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > Flightgear-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/flightgear-devel > -- Sent from my mobile device ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Flightgear-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/flightgear-devel
