Dashboard > OpenFAST > Home > Architecture
OpenFAST Log In | Sign Up   View a printable version of the current page.
Architecture
Added by Jacob Northey, last edited by Jacob Northey on Feb 14, 2008
Labels: 
(None)

Architecture

OpenFAST uses a generic message object model combined with a generic template model.  Each piece of the template model is a part of the decoder/encoder.  By defining a template, the corresponding decoder and encoder are built-in to the template definition.

Pros

  • No recompilation or code-generation is needed as templates change
  • New templates can be loaded on the fly
  • Dynamic template exchange is simple and relatively straight forward
  • Getting up and running with OpenFAST is much easier and faster than code generated solutions
  • More flexible and easier to change than hard-coded template encoder/decoder implementations

Cons 

  • Memory consumption is high due to the fact that all data is stored as objects in the generic object model
  • Performance is lower than FAST implementations using code generation

Site powered by a free Open Source Project / Non-profit License (more) of Confluence - the Enterprise wiki.
Learn more or evaluate Confluence for your organisation.
Powered by Atlassian Confluence, the Enterprise Wiki. (Version: 2.1.5a Build:#411 Mar 16, 2006) - Bug/feature request - Contact Administrators

SourceForge.net Logo