[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[taler-docs] branch master updated: -update spec following #6942
From: |
gnunet |
Subject: |
[taler-docs] branch master updated: -update spec following #6942 |
Date: |
Sun, 01 Aug 2021 11:42:05 +0200 |
This is an automated email from the git hooks/post-receive script.
grothoff pushed a commit to branch master
in repository docs.
The following commit(s) were added to refs/heads/master by this push:
new a52f2c7 -update spec following #6942
a52f2c7 is described below
commit a52f2c77edab063734abcd1cc736367d3d1d4be5
Author: Christian Grothoff <christian@grothoff.org>
AuthorDate: Sun Aug 1 11:41:55 2021 +0200
-update spec following #6942
---
core/api-merchant.rst | 7 +++----
1 file changed, 3 insertions(+), 4 deletions(-)
diff --git a/core/api-merchant.rst b/core/api-merchant.rst
index ac2ba86..8a39278 100644
--- a/core/api-merchant.rst
+++ b/core/api-merchant.rst
@@ -1477,9 +1477,8 @@ Reserving inventory
interface LockRequest {
// UUID that identifies the frontend performing the lock
- // It is suggested that clients use a timeflake for this,
- // see https://github.com/anthonynsimon/timeflake
- lock_uuid: UUID;
+ // Must be unique for the lifetime of the lock.
+ lock_uuid: String;
// How long does the frontend intend to hold the lock?
duration: RelativeTime;
@@ -1603,7 +1602,7 @@ Creating orders
// be used in case different UUIDs were used for different
// products (i.e. in case the user started with multiple
// shopping sessions that were combined during checkout).
- lock_uuids?: UUID[];
+ lock_uuids: String[];
// Should a token for claiming the order be generated?
// False can make sense if the ORDER_ID is sufficiently
--
To stop receiving notification emails like this one, please contact
gnunet@gnunet.org.
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- [taler-docs] branch master updated: -update spec following #6942,
gnunet <=