Very well! Your work goes along my thoughts. But never forget to keep it as simply and as fail proof as possible. We want something for the next eternity.
I think, we need a concept for a central ATC instance: (maybe automated) - For issuing flight plans etc (the individual human ATCs can retrieve it from there (via his application)) - Integrated into ATC App - which ATC position is already occupied => select ATC callsign - which ATC needs support because there is too much to do - transition of targets - which ATC controls which radar contact - ATC intercom (maybe via special FGCOM frequencies?) I see the ATC application as client for this central instance, making its features visible. Flightplans are available via the flight strips, also extra information is transferred from one ATC to the other)... Everything should work without the central instance... But please keep it simple and flexible, so that we don't run into a hell of conflicts between webservice (server / clien) versions and libraries. If I could chosse, I would prefer a non webservice protocol... W.
signature.asc
Description: This is a digitally signed message part
------------------------------------------------------------------------------ Master Visual Studio, SharePoint, SQL, ASP.NET, C# 2012, HTML5, CSS, MVC, Windows 8 Apps, JavaScript and much more. Keep your skills current with LearnDevNow - 3,200 step-by-step video tutorials by Microsoft MVPs and experts. SALE $99.99 this month only -- learn more at: http://p.sf.net/sfu/learnmore_122412
_______________________________________________ Flightgear-devel mailing list Flightgear-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/flightgear-devel
