mirror of
https://github.com/corda/corda.git
synced 2025-02-20 17:33:15 +00:00
Address review comments
This commit is contained in:
parent
7548c6c901
commit
55a33acc32
@ -18,8 +18,8 @@ to agree on to remain in sync.
|
||||
In Corda 3 the right way to run a test network is through distribution of the relevant files via your own mechanisms.
|
||||
We provide a tool to automate the bulk of this task (see below).
|
||||
|
||||
HTTP network map service
|
||||
------------------------
|
||||
HTTP network map protocol
|
||||
-------------------------
|
||||
|
||||
If the node is configured with the ``compatibilityZoneURL`` config then it first uploads its own signed ``NodeInfo``
|
||||
to the server (and each time it changes on startup) and then proceeds to download the entire network map. The network map
|
||||
@ -43,7 +43,7 @@ The set of REST end-points for the network map service are as follows.
|
||||
+----------------+-----------------------------------------+----------------------------------------------------------------------------------------------------------------------------------------------+
|
||||
|
||||
We use HTTP is used for the network map service instead of Corda's own AMQP based peer to peer messaging protocol to
|
||||
enable the server to be placed behind caching content delivery networks like Cloudflare, Akamai, Amazon S3 and so on.
|
||||
enable the server to be placed behind caching content delivery networks like Cloudflare, Akamai, Amazon Cloudfront and so on.
|
||||
By using industrial HTTP cache networks the map server can be shielded from DoS attacks more effectively. Additionally,
|
||||
for the case of distributing small files that rarely change, HTTP is a well understood and optimised protocol. Corda's
|
||||
own protocol is designed for complex multi-way conversations between authenticated identities using signed binary
|
||||
@ -117,8 +117,8 @@ Network parameters update process
|
||||
---------------------------------
|
||||
|
||||
In case of the need to change network parameters Corda zone operator will start the update process. There are many reasons
|
||||
that may lead to this decision: new fields that were added to enable smooth network interoperability, or a change
|
||||
of the existing compatibility constants is required, for example.
|
||||
that may lead to this decision: adding a notary, setting new fields that were added to enable smooth network interoperability,
|
||||
or a change of the existing compatibility constants is required, for example.
|
||||
|
||||
.. note:: A future release may support the notion of phased rollout of network parameter changes.
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user