fluencelabs/gitbook-docs
1
0
Fork 0
mirror of https://github.com/fluencelabs/gitbook-docs synced 2025-04-24 15:32:18 +00:00
Code Issues Projects Releases Wiki Activity

Merge pull request #21 from elmol/2.0.0

Browse Source 
fixing typo in function sayHello
This commit is contained in:
boneyard93501 2021-09-10 03:03:06 -05:00 committed by GitHub
commit e7a387940a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
quick-start/3.-browser-to-service.md
View File

@ -31,7 +31,7 @@ And let's work it from the top:
* Specify the `HelloPeer` interface and function binding \(15-16\) for the local service
* Create the Aqua workflow function `sayHello` \(18-29\)
Before we dive into the `sayHelo` function, let's look at why we still need a local service even though we deployed a hosted service. The reason for that lies in the need for the browser client to be able to consume the message sent from the other browser through the relay peer. With that out of the way, let's dig in:
Before we dive into the `sayHello` function, let's look at why we still need a local service even though we deployed a hosted service. The reason for that lies in the need for the browser client to be able to consume the message sent from the other browser through the relay peer. With that out of the way, let's dig in:
* The function signature \(18\) takes two arguments: `targetPeerId`, which is the client peer id of the other browser and the `targetelayPeerId`, which is the relay id -- both parameters are the values you copy and pasted from the second browser tab into the first browser tab
* The first step is to call on the hosted service `HelloWorld` on the host peer `helloWorldPeerId` , which we specified in line 1