From aa72a53f03be6dcd50e0a750064b5c4e5be2c9f9 Mon Sep 17 00:00:00 2001 From: GuiWar <120386099+GuiWar@users.noreply.github.com> Date: Wed, 6 Dec 2023 08:02:56 -0300 Subject: [PATCH 1/9] Update 02_basics.md Update request server naming rule --- docs/03_server/03_request-server/02_basics.md | 20 ++++++++++++++++++- 1 file changed, 19 insertions(+), 1 deletion(-) diff --git a/docs/03_server/03_request-server/02_basics.md b/docs/03_server/03_request-server/02_basics.md index 8af310bfc4..7c199fe80a 100644 --- a/docs/03_server/03_request-server/02_basics.md +++ b/docs/03_server/03_request-server/02_basics.md @@ -34,7 +34,25 @@ requestReplies { ## Adding a name -Every `requestReply` in your .kts must have a unique name. If you do not provide one, it will be allocated automatically. In the previous example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. +Every `requestReply` in your .kts must have a unique name. The Genesis platform will add a prefix `REQ_` to the resource name. For example, the following code block specify a `requestReply` called `ALL_COUNTERPARTIES`: + +```kotlin +requestReplies { + requestReply("ALL_COUNTERPARTIES", COUNTERPARTY) + ... +} +``` + +To access this request server, you need to call `REQ_ALL_COUNTERPARTIES`. + +If you do not provide one, it will be allocated automatically. In the following example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. + +```kotlin +requestReplies { + requestReply(INSTRUMENT_DETAILS) + ... +} +``` ## Multiple Request Servers From 159e09295d8085026e6d55912e177068cfbccbb7 Mon Sep 17 00:00:00 2001 From: GuiWar <120386099+GuiWar@users.noreply.github.com> Date: Wed, 6 Dec 2023 08:05:13 -0300 Subject: [PATCH 2/9] Update 02_basics.md update previous version --- .../03_server/03_request-server/02_basics.md | 16 +++++++++++----- 1 file changed, 11 insertions(+), 5 deletions(-) diff --git a/versioned_docs/version-previous/03_server/03_request-server/02_basics.md b/versioned_docs/version-previous/03_server/03_request-server/02_basics.md index 8af310bfc4..891ad4b3e1 100644 --- a/versioned_docs/version-previous/03_server/03_request-server/02_basics.md +++ b/versioned_docs/version-previous/03_server/03_request-server/02_basics.md @@ -34,17 +34,23 @@ requestReplies { ## Adding a name -Every `requestReply` in your .kts must have a unique name. If you do not provide one, it will be allocated automatically. In the previous example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. +Every `requestReply` in your .kts must have a unique name. The Genesis platform will add a prefix `REQ_` to the resource name. For example, the following code block specify a `requestReply` called `ALL_COUNTERPARTIES`: -## Multiple Request Servers +```kotlin +requestReplies { + requestReply("ALL_COUNTERPARTIES", COUNTERPARTY) + ... +} +``` + +To access this request server, you need to call `REQ_ALL_COUNTERPARTIES`. -Almost certainly, your application will need to have more than one `requestReply`. So, let us state the obvious and show you a file with two `requestReply` codeblocks. Again, each is the simplest kind you could possibly have. +If you do not provide one, it will be allocated automatically. In the following example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. ```kotlin requestReplies { - requestReply(COUNTERPARTY) - requestReply(INSTRUMENT_DETAILS) + ... } ``` From 5ffe0de689b0ac9102fe3e75ce4d661ea9068237 Mon Sep 17 00:00:00 2001 From: wjhendry <90383531+wjhendry@users.noreply.github.com> Date: Wed, 6 Dec 2023 14:33:12 +0000 Subject: [PATCH 3/9] Update 02_basics.md --- docs/03_server/03_request-server/02_basics.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/03_server/03_request-server/02_basics.md b/docs/03_server/03_request-server/02_basics.md index 7c199fe80a..4373a9ae7b 100644 --- a/docs/03_server/03_request-server/02_basics.md +++ b/docs/03_server/03_request-server/02_basics.md @@ -34,7 +34,7 @@ requestReplies { ## Adding a name -Every `requestReply` in your .kts must have a unique name. The Genesis platform will add a prefix `REQ_` to the resource name. For example, the following code block specify a `requestReply` called `ALL_COUNTERPARTIES`: +Every `requestReply` in your .kts must have a unique name. The Genesis platform will add the prefix `REQ_` to the resource name. For example, the following code block specify a `requestReply` called `ALL_COUNTERPARTIES`: ```kotlin requestReplies { @@ -43,9 +43,9 @@ requestReplies { } ``` -To access this request server, you need to call `REQ_ALL_COUNTERPARTIES`. +To access this `requestReply`, you need to call `REQ_ALL_COUNTERPARTIES`. -If you do not provide one, it will be allocated automatically. In the following example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. +If you do not provide a name for the `requestReply`, it will be allocated automatically. In the following example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. ```kotlin requestReplies { From c8933f62722d0d07faed477421c095bb9d3a7875 Mon Sep 17 00:00:00 2001 From: wjhendry <90383531+wjhendry@users.noreply.github.com> Date: Wed, 6 Dec 2023 14:34:38 +0000 Subject: [PATCH 4/9] Update 02_basics.md --- .../03_server/03_request-server/02_basics.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/versioned_docs/version-previous/03_server/03_request-server/02_basics.md b/versioned_docs/version-previous/03_server/03_request-server/02_basics.md index 891ad4b3e1..f4248ba453 100644 --- a/versioned_docs/version-previous/03_server/03_request-server/02_basics.md +++ b/versioned_docs/version-previous/03_server/03_request-server/02_basics.md @@ -34,7 +34,7 @@ requestReplies { ## Adding a name -Every `requestReply` in your .kts must have a unique name. The Genesis platform will add a prefix `REQ_` to the resource name. For example, the following code block specify a `requestReply` called `ALL_COUNTERPARTIES`: +Every `requestReply` in your .kts must have a unique name. The Genesis platform will add the prefix `REQ_` to the resource name. For example, the following code block specifies a `requestReply` called `ALL_COUNTERPARTIES`: ```kotlin requestReplies { @@ -43,9 +43,10 @@ requestReplies { } ``` -To access this request server, you need to call `REQ_ALL_COUNTERPARTIES`. +To access this `requestReply`, you need to call `REQ_ALL_COUNTERPARTIES`. + +If you do not provide a name for the `requestReply`, it will be allocated automatically. In the following example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. -If you do not provide one, it will be allocated automatically. In the following example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. ```kotlin requestReplies { From 5b53f8e1d948a0805910ba2eb2fb777df2bab212 Mon Sep 17 00:00:00 2001 From: wjhendry <90383531+wjhendry@users.noreply.github.com> Date: Wed, 6 Dec 2023 14:35:53 +0000 Subject: [PATCH 5/9] Update 02_basics.md --- docs/03_server/03_request-server/02_basics.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/03_server/03_request-server/02_basics.md b/docs/03_server/03_request-server/02_basics.md index 4373a9ae7b..d9d6c11c67 100644 --- a/docs/03_server/03_request-server/02_basics.md +++ b/docs/03_server/03_request-server/02_basics.md @@ -34,7 +34,7 @@ requestReplies { ## Adding a name -Every `requestReply` in your .kts must have a unique name. The Genesis platform will add the prefix `REQ_` to the resource name. For example, the following code block specify a `requestReply` called `ALL_COUNTERPARTIES`: +Every `requestReply` in your .kts must have a unique name. The Genesis platform will add the prefix `REQ_` to the resource name. For example, the following code block specifies a `requestReply` called `ALL_COUNTERPARTIES`: ```kotlin requestReplies { From 09e1e9c58cf710307cc50db8d110c679c5b61350 Mon Sep 17 00:00:00 2001 From: wjhendry <90383531+wjhendry@users.noreply.github.com> Date: Wed, 6 Dec 2023 15:44:37 +0000 Subject: [PATCH 6/9] Update 02_basics.md --- docs/03_server/03_request-server/02_basics.md | 16 ++++++---------- 1 file changed, 6 insertions(+), 10 deletions(-) diff --git a/docs/03_server/03_request-server/02_basics.md b/docs/03_server/03_request-server/02_basics.md index d9d6c11c67..c80bdc1187 100644 --- a/docs/03_server/03_request-server/02_basics.md +++ b/docs/03_server/03_request-server/02_basics.md @@ -34,7 +34,10 @@ requestReplies { ## Adding a name -Every `requestReply` in your .kts must have a unique name. The Genesis platform will add the prefix `REQ_` to the resource name. For example, the following code block specifies a `requestReply` called `ALL_COUNTERPARTIES`: +Every `requestReply` in your .kts must have a unique name. If you don't give the `requestReply` a name, the platform will create a name, based on the table or view. In our example above, no name has been supplied. The table used is INSTRUMENT_DETAILS, so the platform calls this `requestReply` REQ_INSTRUMENT_DETAILS. + +It is easy to specify a name for the `requestReply`. For example, here we are calling our `requestReply` ALL_COUNTERPARTIES: + ```kotlin requestReplies { @@ -43,16 +46,9 @@ requestReplies { } ``` -To access this `requestReply`, you need to call `REQ_ALL_COUNTERPARTIES`. - -If you do not provide a name for the `requestReply`, it will be allocated automatically. In the following example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. +When you run `genesisInstall`, the Genesis platform adds the prefix `REQ_` to the name you have specified. So, in the example above, the `requestReply` becomes REQ_ALL_COUNTERPARTIES. That is the name you will need to use when you access this `requestReply`. -```kotlin -requestReplies { - requestReply(INSTRUMENT_DETAILS) - ... -} -``` +So, all the resources in your Request Server have names beginning with REQ_ regardless of whether you specify a name. ## Multiple Request Servers From 3780d72c3235a64b4bb0d33e6fd2ce6e51bd9f82 Mon Sep 17 00:00:00 2001 From: wjhendry <90383531+wjhendry@users.noreply.github.com> Date: Wed, 6 Dec 2023 15:47:02 +0000 Subject: [PATCH 7/9] Update 02_basics.md --- .../03_server/03_request-server/02_basics.md | 17 ++++++----------- 1 file changed, 6 insertions(+), 11 deletions(-) diff --git a/versioned_docs/version-previous/03_server/03_request-server/02_basics.md b/versioned_docs/version-previous/03_server/03_request-server/02_basics.md index f4248ba453..885124db46 100644 --- a/versioned_docs/version-previous/03_server/03_request-server/02_basics.md +++ b/versioned_docs/version-previous/03_server/03_request-server/02_basics.md @@ -34,7 +34,10 @@ requestReplies { ## Adding a name -Every `requestReply` in your .kts must have a unique name. The Genesis platform will add the prefix `REQ_` to the resource name. For example, the following code block specifies a `requestReply` called `ALL_COUNTERPARTIES`: +Every `requestReply` in your .kts must have a unique name. If you don't give the `requestReply` a name, the platform will create a name, based on the table or view. In our example above, no name has been supplied. The table used is INSTRUMENT_DETAILS, so the platform calls this `requestReply` REQ_INSTRUMENT_DETAILS. + +It is easy to specify a name for the `requestReply`. For example, here we are calling our `requestReply` ALL_COUNTERPARTIES: + ```kotlin requestReplies { @@ -43,17 +46,9 @@ requestReplies { } ``` -To access this `requestReply`, you need to call `REQ_ALL_COUNTERPARTIES`. - -If you do not provide a name for the `requestReply`, it will be allocated automatically. In the following example, the `requestReply` will automatically be named as `REQ_INSTRUMENT_DETAILS` - based on the table name. +When you run `genesisInstall`, the Genesis platform adds the prefix `REQ_` to the name you have specified. So, in the example above, the `requestReply` becomes REQ_ALL_COUNTERPARTIES. That is the name you will need to use when you access this `requestReply`. - -```kotlin -requestReplies { - requestReply(INSTRUMENT_DETAILS) - ... -} -``` +So, all the resources in your Request Server have names beginning with REQ_ regardless of whether you specify a name. ## Specifying fields on request and reply With all the `requestReply` codeblocks we have seen so far, all the fields in the table are returned. From 3d4555a75345e0995fe9cc5295d1df8dd37b688e Mon Sep 17 00:00:00 2001 From: wjhendry <90383531+wjhendry@users.noreply.github.com> Date: Wed, 6 Dec 2023 16:00:33 +0000 Subject: [PATCH 8/9] Update 02_basics.md --- .../03_server/03_request-server/02_basics.md | 12 +++++++++++- 1 file changed, 11 insertions(+), 1 deletion(-) diff --git a/versioned_docs/version-previous/03_server/03_request-server/02_basics.md b/versioned_docs/version-previous/03_server/03_request-server/02_basics.md index 885124db46..95f5fe517a 100644 --- a/versioned_docs/version-previous/03_server/03_request-server/02_basics.md +++ b/versioned_docs/version-previous/03_server/03_request-server/02_basics.md @@ -32,9 +32,19 @@ requestReplies { } ``` +Almost certainly, your application will need to have more than one `requestReply`. So, let us state the obvious and show you a file with two `requestReply` codeblocks. Again, each is the simplest kind you could possibly have. + +```kotlin +requestReplies { + requestReply(COUNTERPARTY) + + requestReply(INSTRUMENT_DETAILS) +} +``` + ## Adding a name -Every `requestReply` in your .kts must have a unique name. If you don't give the `requestReply` a name, the platform will create a name, based on the table or view. In our example above, no name has been supplied. The table used is INSTRUMENT_DETAILS, so the platform calls this `requestReply` REQ_INSTRUMENT_DETAILS. +Every `requestReply` in your .kts must have a unique name. If you don't give the `requestReply` a name, the platform will create a name, based on the table or view. In the first example above, no name has been supplied. The table used is INSTRUMENT_DETAILS, so the platform calls this `requestReply` REQ_INSTRUMENT_DETAILS. It is easy to specify a name for the `requestReply`. For example, here we are calling our `requestReply` ALL_COUNTERPARTIES: From 6626c739c5890797d7fbf8c5b6a8c9164211d4b4 Mon Sep 17 00:00:00 2001 From: wjhendry <90383531+wjhendry@users.noreply.github.com> Date: Wed, 6 Dec 2023 16:03:01 +0000 Subject: [PATCH 9/9] Update 02_basics.md --- docs/03_server/03_request-server/02_basics.md | 24 +++++++++---------- 1 file changed, 11 insertions(+), 13 deletions(-) diff --git a/docs/03_server/03_request-server/02_basics.md b/docs/03_server/03_request-server/02_basics.md index c80bdc1187..95f5fe517a 100644 --- a/docs/03_server/03_request-server/02_basics.md +++ b/docs/03_server/03_request-server/02_basics.md @@ -32,9 +32,19 @@ requestReplies { } ``` +Almost certainly, your application will need to have more than one `requestReply`. So, let us state the obvious and show you a file with two `requestReply` codeblocks. Again, each is the simplest kind you could possibly have. + +```kotlin +requestReplies { + requestReply(COUNTERPARTY) + + requestReply(INSTRUMENT_DETAILS) +} +``` + ## Adding a name -Every `requestReply` in your .kts must have a unique name. If you don't give the `requestReply` a name, the platform will create a name, based on the table or view. In our example above, no name has been supplied. The table used is INSTRUMENT_DETAILS, so the platform calls this `requestReply` REQ_INSTRUMENT_DETAILS. +Every `requestReply` in your .kts must have a unique name. If you don't give the `requestReply` a name, the platform will create a name, based on the table or view. In the first example above, no name has been supplied. The table used is INSTRUMENT_DETAILS, so the platform calls this `requestReply` REQ_INSTRUMENT_DETAILS. It is easy to specify a name for the `requestReply`. For example, here we are calling our `requestReply` ALL_COUNTERPARTIES: @@ -50,18 +60,6 @@ When you run `genesisInstall`, the Genesis platform adds the prefix `REQ_` to th So, all the resources in your Request Server have names beginning with REQ_ regardless of whether you specify a name. -## Multiple Request Servers - -Almost certainly, your application will need to have more than one `requestReply`. So, let us state the obvious and show you a file with two `requestReply` codeblocks. Again, each is the simplest kind you could possibly have. - -```kotlin -requestReplies { - requestReply(COUNTERPARTY) - - requestReply(INSTRUMENT_DETAILS) -} -``` - ## Specifying fields on request and reply With all the `requestReply` codeblocks we have seen so far, all the fields in the table are returned.