You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Summary:
Simplified Networking Guide, based on the old Network polyfill doc.
This guide strongly recommends using fetch, while still informing the user about React Native's support for other libraries.
In order to provide an actual working networking example, a `movies.json` file is added at the root of the site, allowing the user to fetch a small blob of JSON:
```
fetch('http://facebook.github.io/react-native/movies.json')
```

Closesfacebook#8381
Differential Revision: D3479018
Pulled By: lacker
fbshipit-source-id: 1f2078bf2414a13f7f77d5af55b08948909093a3
One of React Native's goals is to be a playground where we can experiment with different architectures and crazy ideas. Since browsers are not flexible enough, we had no choice but to reimplement the entire stack. In the places that we did not intend to change anything, we tried to be as faithful as possible to the browser APIs. The networking stack is a great example.
10
+
Many mobile apps need to load resources from a remote URL. You may want to make a POST request to a REST API, or you may simply need to fetch a chunk of static content from another server.
11
11
12
-
## Fetch
12
+
## Using Fetch
13
13
14
-
[fetch](https://fetch.spec.whatwg.org/) is a better networking API being worked on by the standards committee and is already available in Chrome. It is available in React Native by default.
14
+
React Native provides the [Fetch API](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API) for your networking needs. Fetch will seem familiar if you have used `XMLHttpRequest` or other networking APIs before. You may refer to MDN's guide on [Using Fetch](https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch) for additional information.
15
15
16
-
#### Usage
16
+
#### Making requests
17
+
18
+
In order to fetch content from an arbitrary URL, just pass the URL to fetch:
17
19
18
20
```js
19
-
fetch('https://mywebsite.com/endpoint/')
21
+
fetch('https://mywebsite.com/mydata.json')
20
22
```
21
23
22
-
Include a request object as the optional second argument to customize the HTTP request:
24
+
Fetch also takes an optional second argument that allows you to customize the HTTP request. You may want to specify additional headers, or make a POST request:
Take a look at the [Fetch Request docs](https://developer.mozilla.org/en-US/docs/Web/API/Request) for a full list of properties.
41
+
42
+
#### Handling the response
39
43
40
-
`fetch` returns a [Promise](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) that can be processed in two ways:
44
+
The above examples show how you can make a request. In many cases, you will want to do something with the response.
41
45
42
-
1. Using `then` and `catch` in synchronous code:
46
+
Networking is an inherently asynchronous operation. Fetch methods will return a [Promise](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise) that make it straightforward to write code that works in an asynchronous manner:
2. Called within an asynchronous function using ES7 `async`/`await` syntax:
60
+
61
+
You can also use ES7's `async`/`await` syntax in React Native app:
55
62
56
63
```js
57
-
classMyComponentextendsReact.Component {
58
-
...
59
-
asyncgetUsersFromApi() {
60
-
try {
61
-
let response =awaitfetch('https://mywebsite.com/endpoint/');
62
-
let responseJson =awaitresponse.json();
63
-
returnresponseJson.users;
64
-
} catch(error) {
65
-
// Handle error
66
-
console.error(error);
67
-
}
64
+
asyncgetMoviesFromApi() {
65
+
try {
66
+
let response =awaitfetch('http://facebook.github.io/react-native/movies.json');
67
+
let responseJson =awaitresponse.json();
68
+
returnresponseJson.movies;
69
+
} catch(error) {
70
+
console.error(error);
68
71
}
69
-
...
70
72
}
71
73
```
72
74
73
-
- Note: Errors thrown by rejected Promises need to be caught, or they will be swallowed silently
75
+
Don't forget to catch any errors that may be thrown by `fetch`, otherwise they will be dropped silently.
74
76
75
-
##WebSocket
77
+
### Using Other Networking Libraries
76
78
77
-
WebSocket is a protocol providing full-duplex communication channels over a single TCP connection.
78
-
79
-
```js
80
-
var ws =newWebSocket('ws://host.com/path');
81
-
82
-
ws.onopen= () => {
83
-
// connection opened
84
-
ws.send('something');
85
-
};
86
-
87
-
ws.onmessage= (e) => {
88
-
// a message was received
89
-
console.log(e.data);
90
-
};
91
-
92
-
ws.onerror= (e) => {
93
-
// an error occurred
94
-
console.log(e.message);
95
-
};
96
-
97
-
ws.onclose= (e) => {
98
-
// connection closed
99
-
console.log(e.code, e.reason);
100
-
};
101
-
```
102
-
103
-
## XMLHttpRequest
104
-
105
-
XMLHttpRequest API is implemented on-top of [iOS networking apis](https://developer.apple.com/library/mac/documentation/Cocoa/Conceptual/URLLoadingSystem/URLLoadingSystem.html) and [OkHttp](http://square.github.io/okhttp/). The notable difference from web is the security model: you can read from arbitrary websites on the internet since there is no concept of [CORS](http://en.wikipedia.org/wiki/Cross-origin_resource_sharing).
79
+
The [XMLHttpRequest API](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) is built in to React Native. This means that you can use third party libraries such as [frisbee](https://github.com/niftylettuce/frisbee) or [axios](https://github.com/mzabriskie/axios) that depend on it, or you can use the XMLHttpRequest API directly if you prefer.
> The security model for XMLHttpRequest is different than on web as there is no concept of [CORS](http://en.wikipedia.org/wiki/Cross-origin_resource_sharing) in native apps.
100
+
101
+
## WebSocket Support
102
+
103
+
React Native supports [WebSocket](https://developer.mozilla.org/en-US/docs/Web/API/WebSocket), a protocol which provides full-duplex communication channels over a single TCP connection.
Please follow the [MDN Documentation](https://developer.mozilla.org/en-US/docs/Web/API/XMLHttpRequest) for a complete description of the API.
154
-
155
-
As a developer, you're probably not going to use XMLHttpRequest directly as its API is very tedious to work with. But the fact that it is implemented and compatible with the browser API gives you the ability to use third-party libraries such as [frisbee](https://github.com/niftylettuce/frisbee) or [axios](https://github.com/mzabriskie/axios) directly from npm.
0 commit comments