braid-http 1.3.59 → 1.3.60
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +15 -8
- package/package.json +1 -1
package/README.md
CHANGED
|
@@ -1,11 +1,18 @@
|
|
|
1
1
|
# Braid-HTTP
|
|
2
2
|
|
|
3
|
-
This
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
3
|
+
This [ponyfill](https://ponyfill.com/) library extends the HTTP
|
|
4
|
+
implementations of Browsers and Nodejs with Braid-HTTP; transforming them from
|
|
5
|
+
*state transfer* to *state synchronization* systems.
|
|
6
|
+
|
|
7
|
+
These features are provided in an elegant, backwards-compatible way:
|
|
8
|
+
- Browsers: get a drop-in replacement for `fetch()`
|
|
9
|
+
- Nodejs: get a route handler that adds abilities to the `http`, `https`, and `http2` modules
|
|
10
|
+
|
|
11
|
+
It conforms to the [Braid-HTTP
|
|
12
|
+
v04](https://github.com/braid-org/braid-spec/blob/master/draft-toomim-httpbis-braid-http-04.txt)
|
|
13
|
+
specification, with the additional [HTTP
|
|
14
|
+
Multiresponse](https://braid.org/meeting-89) and [Multiplexing
|
|
15
|
+
v1.0](https://braid.org/protocol/multiplexing) extensions.
|
|
9
16
|
|
|
10
17
|
Developed in [braid.org](https://braid.org).
|
|
11
18
|
|
|
@@ -163,7 +170,7 @@ require('http').createServer(
|
|
|
163
170
|
version: ['greg'],
|
|
164
171
|
body: JSON.stringify({greg: 'greg'})
|
|
165
172
|
})
|
|
166
|
-
}
|
|
173
|
+
})
|
|
167
174
|
).listen(9935)
|
|
168
175
|
```
|
|
169
176
|
|
|
@@ -284,4 +291,4 @@ response connection dies, and thus you cannot attach a `.catch()` handler to
|
|
|
284
291
|
automatically reconnect. (See
|
|
285
292
|
[issue #980](https://github.com/node-fetch/node-fetch/issues/980) and
|
|
286
293
|
[#753](https://github.com/node-fetch/node-fetch/issues/753).) We recommend
|
|
287
|
-
using the `http`
|
|
294
|
+
using the `http` client on nodejs instead.
|