This page is no more maintained, the current one is at http://www.tiian.org/flom/libflom/libflom_for_CXX_developers.html
FLoM API is very easy to understand and use; these are the basic concepts:
BasicStatic.cc example can be considered the hello world FLoM equivalent for static programming style:
1. allocate a FlomHandle object on the stack declaring it
2. synchronize your program using method lock()
3. do everything your program must perform inside the synchronization window
5. deserialize your program using method unlock()
Note: C++ clean-ups every statically initialized FlomHandle object for you: you don't have to mind about memory leaks.
BasicDynamic.cc example can be considered the hello world FLoM equivalent for dynamic programming style:
1. declare a FlomHandle object pointer
2. create a new object using new
3. synchronize your program using method lock()
4. do everything your program must perform inside the synchronization window
5. desynchronize your program using method unlock()
6. delete the object using delete
Note: you must delete every created FlomHandle object; if you don't delete every object you will generate memory leaks.
Basic examples do not explain as you can specify the name of the logical resource, the quantity of a numerical resource and the other parameters you typically use with flom command line.
AdvancedStatic.cc and AdvancedDynamic.cc examples show how some properties can be set before entering in the synchronization phase.
The complete list of the available setter/getter methods can be retrieved from:
Some resources, for example unique sequences, can be declared as transactional.
A transactional resource has an associated state and it needs an explicit unlock to commit the state.
If a transactional resource is not committed due to a program crash, the state will be rolled back.
Method unlockRollback has been introduced to force a state rollback during the unlock phase, even if a program does not crash.
An example is available in this source code: Transactional.cc.