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
+5-2Lines changed: 5 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -30,14 +30,14 @@ Then you can refer to seatsio-java as a regular package:
30
30
```
31
31
// build.gradle
32
32
dependencies {
33
-
compile 'com.github.seatsio:seatsio-java:70.1.0'
33
+
compile 'com.github.seatsio:seatsio-java:70.2.0'
34
34
}
35
35
36
36
// pom.xml
37
37
<dependency>
38
38
<groupId>com.github.seatsio</groupId>
39
39
<artifactId>seatsio-java</artifactId>
40
-
<version>70.1.0</version>
40
+
<version>70.2.0</version>
41
41
</dependency>
42
42
```
43
43
@@ -260,3 +260,6 @@ It's perfectly fine to re-use an instance of `SeatsioClient` in different thread
260
260
We manage a connection pool under the hood, to avoid having to reconnect to the seats.io server on every call. This pool supports 200 concurrent connections.
261
261
262
262
The connection pool is shared between all instances of `SeatsioClient`.
263
+
264
+
In some cases, e.g. when you're running automated test suite against a seats.io stub, it may be useful to reset the connection pool between tests.
265
+
To do so, call `seatsioClient.reinitializeHttpConnectionPool()`.
0 commit comments