High-Level Architecture: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
No edit summary |
||
Line 6: | Line 6: | ||
{{FGCquote|1= Moving toward a new modular HLA architecture offers a number of possibilities. One of these is that different modules, or subsystems, can effectively become independent binaries. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34196458/ | title = <nowiki>Re: [Flightgear-devel] Policy Document and V4.X Roadmap</nowiki> | author = <nowiki>Durk Talsma</nowiki> | date = Jun 11th, 2015 }}}} | {{FGCquote|1= Moving toward a new modular HLA architecture offers a number of possibilities. One of these is that different modules, or subsystems, can effectively become independent binaries. |2= {{cite web | url = http://sourceforge.net/p/flightgear/mailman/message/34196458/ | title = <nowiki>Re: [Flightgear-devel] Policy Document and V4.X Roadmap</nowiki> | author = <nowiki>Durk Talsma</nowiki> | date = Jun 11th, 2015 }}}} | ||
{{FGCquote | |||
|1= In terms of integration with the property tree, I'm thinking that in the short term all the different components that we split out into separate threads or executables will simply use their own properties trees, and use the RTI to reflect the particular (minimal) data that needs to be passed between components. | |||
|2= {{cite web | |||
| url = http://sourceforge.net/p/flightgear/mailman/message/34632142/ | |||
| title = <nowiki>Re: [Flightgear-devel] HLA developments</nowiki> | |||
| author = <nowiki>Stuart Buchanan</nowiki> | |||
| date = Nov 19th, 2015 | |||
}} | |||
}} | |||
{{FGCquote | {{FGCquote |
Revision as of 13:57, 19 November 2015
Multicore |
---|
Configuration |
Ongoing Efforts |
Proposals & RFCs |
Background |
For developers |
High-Level Architecture (HLA) is a general purpose architecture for distributed computer simulation systems.
Using a HLA, computer simulations can interact with other computer simulations regardless of the computing platforms. The interactions between the simulations are managed by a Run-Time Infrastructure (RTI).
Moving toward a new modular HLA architecture offers a number of possibilities. One of these is that different modules, or subsystems, can effectively become independent binaries. — Durk Talsma (Jun 11th, 2015). Re: [Flightgear-devel] Policy Document and V4.X Roadmap.
(powered by Instant-Cquotes) |
In terms of integration with the property tree, I'm thinking that in the short term all the different components that we split out into separate threads or executables will simply use their own properties trees, and use the RTI to reflect the particular (minimal) data that needs to be passed between components. — Stuart Buchanan (Nov 19th, 2015). Re: [Flightgear-devel] HLA developments.
(powered by Instant-Cquotes) |
For additional information, please see FlightGear HLA support (High Level Architecture). Also see FlightGear CIGI Support (Common Image Generator Interface).
External links
- High-level architecture (simulation) on Wikipedia