/history API semantics extended.

That API has now a new 'ordering' flag that lets the
client choose what ordering the results should have:
ascending or descending.

In particular, this change adapted the fakebank and
tests logic to such introduction.

1 files changed, 3 insertions, 1 deletions

diff --git a/src/include/taler_testing_bank_lib.h b/src/include/taler_testing_bank_lib.h
index fd027c5b8..a3cc741e6 100644
--- a/src/include/taler_testing_bank_lib.h
+++ b/src/include/taler_testing_bank_lib.h
@@ -90,7 +90,8 @@ TALER_TESTING_prepare_bank (const char *config_filename);
  *        operation.
  * @param account_no bank account number to ask the history for.
  * @param direction which direction this operation is interested
- *        in.
+ * @param ascending if GNUNET_YES, it ask the bank to return results
+ *        in chronological order.
  * @param start_row_reference reference to a command that can
  *        offer a row identifier, to be used as the starting row
  *        to accept in the result.
@@ -104,6 +105,7 @@ TALER_TESTING_cmd_bank_history
    const char *bank_url,
    uint64_t account_no,
    enum TALER_BANK_Direction direction,
+   unsigned int ascending,
    const char *start_row_reference,
    long long num_results);