Skip to content

Commit 4df7c87

Browse files
committed
Add delay-sensitivity discussion...
...as "when not to deplay a gateway" Ref #93
1 parent b652639 commit 4df7c87

File tree

1 file changed

+11
-0
lines changed

1 file changed

+11
-0
lines changed

content/guides/concepts/ipfs-gateway.md

Lines changed: 11 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -54,11 +54,14 @@ Regardless of who deploys it and where, any IPFS gateway resolves access to any
5454

5555
## What types of IPFS gateways exist?
5656

57+
The discussion above illustrated the use of read-only HTTP(S) gateways to fetch content. Other types of gateways exist as well:
58+
5759
| gateway type | sub-type | functional description |
5860
| -----------: | :------- | :-- |
5961
| HTTP | readable | Only retrieves content (HTTP GET method) |
6062
| | writeable | Allows data to be added to IPFS (HTTP POST, PUT, DELETE methods) |
6163

64+
6265
<!-- Explain exceptions in Limitations section -->
6366

6467

@@ -74,6 +77,14 @@ Regardless of who deploys it and where, any IPFS gateway resolves access to any
7477

7578
## When not to provide a gateway
7679

80+
### Delay-sensitive applications
81+
Any gateway introduces delay in completing desired actions.
82+
Faster execution occurs when using methods at the top of the following list:
83+
* native IPFS node embedded within the app.
84+
* IPFS extension to app.
85+
* gateway installed as a local service on the app's machine, with redirection of requests
86+
from app to the local service.
87+
* public/private gateways.
7788

7889
## Limitations
7990

0 commit comments

Comments
 (0)