8ac4bc1d58
Reasons: 1. The protocol should not depend upon implementation details such as how the database objects are structured or reflected 2. The protocol should deal in abstract concepts 3. Should use fc::datastream rather than istringstream for performance and memory allocation reasons 4. Fees should be charged proportional to the size of the operation 5. Validate on the assert operation should also perform sanity checks on types 6. Protocol definition objects should never depend upon the database because they may be used in situations where the database and evaluators are not present. 7. Reflected field names should never have '_' in them because they become part of the *PUBLIC* json definition. |
||
|---|---|---|
| .. | ||
| app | ||
| benchmarks | ||
| common | ||
| intense | ||
| performance | ||
| tests | ||
| CMakeLists.txt | ||