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
@@ -76,4 +80,53 @@ export function httpBatchConfigurationFactory() {
76
80
exportclassAppModule { }
77
81
```
78
82
83
+
Then you can just use the Http service as you normally would safe in the knowlegde that requests to you batchable service (configured above) will be batched.
Below are all the configuration options for a single batch endpoint. Note that you can have as many batch endpoints as you want but you would need a seperate configuraiton object for each one.
113
+
114
+
### <aname="config-endpointurl"></a> Endpoint Url
115
+
The root endpoint url which is used to determine if the http call is destinted to an endpoint that can be batched.
116
+
For example you endpoint might be:
117
+
118
+
```https://api.myservice.com```
119
+
120
+
Calls to ```https//api.myservice.com/users``` or ```https//api.myservice.com/users/fdfkhdf-3432e23wd/friends?limit=10&from=0``` would be batched.
121
+
Calls to ```https://qa.myservice.com/bugs``` would not be batched as the subdomain are different.
The url of the exposed batch endpoint that is associated with the service defined in rootEndpointUrl.
125
+
126
+
For example
127
+
128
+
```https://api.myservice.com/$batch```
129
+
130
+
### <aname="config-enabled"></a> Enabled
131
+
This optional parameter defaults to true. If false calls that would normally be batched to this endpoint will just be passed through as normal HTTP calls.
0 commit comments