Re: [Mratc-developers] [my status]

[Michael R. <ht...@us...>]

----- Original Message -----
From: "Aquila Deus" <aqu...@ya...>

> Hey! What if we don't deal with the http communcation part? I
mean, just do
> what ATC controllers exactly do (they don't need to worry
about the network
> traffic issue, right?)
>
> We define our own interface to get flights/radar info and send
back messages to
> flights. No need to use network/http/etc. The flights/radar
emulations can be
> done all together, in one program.
>
> Comment?

I think network communication is an important part of
simulation.  One benefit from incorporating network
communication is we can have flight simulations running on
machines all over the world, to better simulate a real load.

During development, we could maybe have a version of the
software that does not incorporate network communications and
later migrate to a version that does.  Maybe function calls in
the preliminary version can be turned into http
requests/responses in later versions.

If you are going to code ATC, radar, and flights all in one
program, maybe classify functions into categories (functions
called by the ATC, radar, flights, or a combination of the
three).  Then, when we want to split up the program later, we
can just copy the appropriate functions into the various
programs.

--Mike