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
Copy file name to clipboardExpand all lines: README.md
+18-17Lines changed: 18 additions & 17 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -27,27 +27,27 @@
27
27
```
28
28
29
29
*Note: The SDK uses a standard interface for the http backend see [HttpClient.](https://github.com/evolv-ai/ascend-java-sdk/blob/master/src/main/java/ai/evolv/HttpClient.java).
30
-
When configuring the client you must specify what implementation of HttpClient to use (or implement your own). See "Custom Http Backend" for more details.*
30
+
When configuring the AscendClient you must specify what implementation of HttpClient to use (or implement your own). See "Custom Http Backend" for more details.*
*Note: The above HttpClient implementation uses org.asynchttpclient:async-http-client as its http client. In order to use
116
+
*Note: Replace 'sandbox' with your own environment id.
117
+
*Note: The above HttpClient implementation uses org.asynchttpclient:async-http-httpClient as its http httpClient. In order to use
117
118
the implementation you will need to bring the package into your dependencies.*
118
119
119
120
### Custom Allocation Store (optional)
120
121
121
122
Once a participant has been allocated into an experiment you may want to retain the allocations they received. To do this, create a custom allocation store by implementing the AscendAllocationStore interface. You can supply the
122
-
custom allocation store to the client when you build the AscendConfig.
123
+
custom allocation store to the AscendClient when you build the AscendConfig.
123
124
124
-
1. Supply the allocation store to the client.
125
+
1. Supply the allocation store to the AscendClient.
0 commit comments