fluencelabs/gitbook-docs
1
0
Fork 0
mirror of https://github.com/fluencelabs/gitbook-docs synced 2025-04-25 07:52:14 +00:00
Code Issues Projects Releases Wiki Activity

GitBook: [2.0.0] 23 pages modified

Browse Source
This commit is contained in:
boneyard93501 2021-08-15 16:25:50 +00:00 committed by gitbook-bot
parent 2b6f070ec5
commit 5afd345b6c
No known key found for this signature in database
GPG Key ID: 07D2180C7B12D0FF
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
quick-start/1.-browser-to-browser-1.md
View File

@ -54,7 +54,7 @@ Which can now be imported into our `App.tsx` file:
![Import Aqua generated Typescript stub \(line 7\)](../.gitbook/assets/image%20%2826%29.png) ![Import Aqua generated Typescript stub \(line 7\)](../.gitbook/assets/image%20%2826%29.png)
Lest it be overlooked, we wrote a little more than a handful of lines of code in Aqua and ended up with a deployment-ready code block that includes both the network routing and a compute logic to facilitate browser-to-browser messaging over a peer-to-peer network. We wrote a little more than a handful of lines of code in Aqua and ended up with a deployment-ready code block that includes both the network routing and a compute logic to facilitate browser-to-browser messaging over a peer-to-peer network.
The local \(browser\) service `HelloPeer` is also implemented in the `App.tsx` file: The local \(browser\) service `HelloPeer` is also implemented in the `App.tsx` file:
@ -62,5 +62,5 @@ The local \(browser\) service `HelloPeer` is also implemented in the `App.tsx` f
To summarize, we run an app that facilities messaging between two browsers over a peer-to-peer network. At the core of this capability is Aqua which allowed us in just a few lines of code to program both the network topology and the application workflow in barely more than a handful of lines of code. Hint: You should be excited. For more information on Aqua, see the [Aqua Book](https://app.gitbook.com/@fluence/s/aqua-book/). To summarize, we run an app that facilities messaging between two browsers over a peer-to-peer network. At the core of this capability is Aqua which allowed us in just a few lines of code to program both the network topology and the application workflow in barely more than a handful of lines of code. Hint: You should be excited. For more information on Aqua, see the [Aqua Book](https://app.gitbook.com/@fluence/s/aqua-book/).
In the next section, we develop a Wasm module and deploy it as a hosted service to the Fluence peer-to-peer network. In the next section, we develop a WebAssembly module and deploy it as a hosted service to the Fluence peer-to-peer network.