-
Notifications
You must be signed in to change notification settings - Fork 146
Design Goals
ffead-cpp does not require application class files to inherit any base classes. You can just implement a method signature and the framework will invoke your control method. Every application class is now just a plain old C++ class and nothing more. There is a small set of XML tags required for configuration in ffead-cpp which are very easy to read and manage. Markers provide the best alternative to XML configuration when it comes to manage and control the flow of your application. Most needed features like Type Conversion, String functions, Logging, Thread-Pools, Serialization and many more make application development super easy.
Modules are the most important feature of ffead-cpp. They provide core functionality to the framework’s upper layers or Handlers/Plugins/Services. A module may provide common functionality like data type conversion, string utilities, compression, crypto utiltities etc, may provide a framework like server-util which can be used to build a high performance server, it may provide a client library for connecting to HTTP/Binary protocol servers, may provide authentication/security capabilities, may provide SSL capabilities, thread features, ORM features, Caching interface features etc. Modules are the basic building blocks of ffead-cpp