mirror of
https://github.com/bigchaindb/js-bigchaindb-driver.git
synced 2024-11-22 01:36:56 +01:00
added versions numbers
This commit is contained in:
parent
99a049056b
commit
0d9d04eb8b
@ -44,8 +44,12 @@ Compatibility Matrix
|
|||||||
Older versions
|
Older versions
|
||||||
--------------------
|
--------------------
|
||||||
|
|
||||||
|
#### Versions 4.x.x
|
||||||
|
|
||||||
|
|
||||||
|
|
||||||
As part of the changes in the BigchainDB 2.0 server, some endpoint were
|
As part of the changes in the BigchainDB 2.0 server, some endpoint were
|
||||||
modified. In order to be consistent with them, the JS driver does not have
|
modified. In order to be consistent with them, the JS driver does not have
|
||||||
anymore the `pollStatusAndFetchTransaction()` method as there are three
|
anymore the `pollStatusAndFetchTransaction()` method as there are three
|
||||||
different ways of posting a transaction.
|
different ways of posting a transaction.
|
||||||
- `async` using the `postTransaction`: the response will return immediately and not wait to see if the transaction is valid.
|
- `async` using the `postTransaction`: the response will return immediately and not wait to see if the transaction is valid.
|
||||||
@ -53,10 +57,12 @@ different ways of posting a transaction.
|
|||||||
- `commit` using the `postTransactionCommit`: the response will return after the transaction is committed to a block.
|
- `commit` using the `postTransactionCommit`: the response will return after the transaction is committed to a block.
|
||||||
|
|
||||||
By default in the docs we will use the `postTransactionCommit` as is way of
|
By default in the docs we will use the `postTransactionCommit` as is way of
|
||||||
being sure that the transaction is validated and commited to a block, so
|
being sure that the transaction is validated and commited to a block, so
|
||||||
there will not be any issue if you try to transfer the asset immediately.
|
there will not be any issue if you try to transfer the asset immediately.
|
||||||
|
|
||||||
|
|
||||||
|
#### Versions 3.2.x
|
||||||
|
|
||||||
For versions below 3.2, a transfer transaction looked like:
|
For versions below 3.2, a transfer transaction looked like:
|
||||||
|
|
||||||
.. code-block:: js
|
.. code-block:: js
|
||||||
@ -89,7 +95,7 @@ transaction should be now:
|
|||||||
|
|
||||||
|
|
||||||
The upgrade allows to create transfer transaction spending outputs that belong
|
The upgrade allows to create transfer transaction spending outputs that belong
|
||||||
to different transactions. So for instance is now possible to create a transfer
|
to different transactions. So for instance is now possible to create a transfer
|
||||||
transaction spending two outputs from two different create transactions:
|
transaction spending two outputs from two different create transactions:
|
||||||
|
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user