Hi folks,
TL;DR: here is -- as promised -- a possible solution how to pool HTTP
sessions with a single HttpClient:
First, I had to create the custom object for holding that session
information:
public class RawSession {
private CookieStore cookieStore;
private MutableInt requestId;
On Wed, 2015-02-11 at 19:36 +0100, Michael Osipov wrote:
Am 2015-01-26 um 10:18 schrieb Oleg Kalnichevski:
On Sun, 2015-01-25 at 22:24 +0100, Michael Osipov wrote:
Am 2015-01-25 um 18:12 schrieb Oleg Kalnichevski:
On Sat, 2015-01-24 at 16:50 +0100, Michael Osipov wrote:
Am 2015-01-24 um
Am 2015-01-26 um 10:18 schrieb Oleg Kalnichevski:
On Sun, 2015-01-25 at 22:24 +0100, Michael Osipov wrote:
Am 2015-01-25 um 18:12 schrieb Oleg Kalnichevski:
On Sat, 2015-01-24 at 16:50 +0100, Michael Osipov wrote:
Am 2015-01-24 um 12:29 schrieb Oleg Kalnichevski:
On Fri, 2015-01-23 at 23:36
On Sun, 2015-01-25 at 22:24 +0100, Michael Osipov wrote:
Am 2015-01-25 um 18:12 schrieb Oleg Kalnichevski:
On Sat, 2015-01-24 at 16:50 +0100, Michael Osipov wrote:
Am 2015-01-24 um 12:29 schrieb Oleg Kalnichevski:
On Fri, 2015-01-23 at 23:36 +0100, Michael Osipov wrote:
Hi folks,
I am
On Sat, 2015-01-24 at 16:50 +0100, Michael Osipov wrote:
Am 2015-01-24 um 12:29 schrieb Oleg Kalnichevski:
On Fri, 2015-01-23 at 23:36 +0100, Michael Osipov wrote:
Hi folks,
I am looking for a design decision to cache session information for a
request workflow embedded in a
Am 2015-01-25 um 18:12 schrieb Oleg Kalnichevski:
On Sat, 2015-01-24 at 16:50 +0100, Michael Osipov wrote:
Am 2015-01-24 um 12:29 schrieb Oleg Kalnichevski:
On Fri, 2015-01-23 at 23:36 +0100, Michael Osipov wrote:
Hi folks,
I am looking for a design decision to cache session information for
Am 2015-01-24 um 12:29 schrieb Oleg Kalnichevski:
On Fri, 2015-01-23 at 23:36 +0100, Michael Osipov wrote:
Hi folks,
I am looking for a design decision to cache session information for a
request workflow embedded in a SOAP/REST-based webapp.
Here is a little background how the workflow is
On Fri, 2015-01-23 at 23:36 +0100, Michael Osipov wrote:
Hi folks,
I am looking for a design decision to cache session information for a
request workflow embedded in a SOAP/REST-based webapp.
Here is a little background how the workflow is structured and what I am
trying to solve:
Hi folks,
I am looking for a design decision to cache session information for a
request workflow embedded in a SOAP/REST-based webapp.
Here is a little background how the workflow is structured and what I am
trying to solve:
Note: I have read the entire tutorial and am somewhat overwhelmed
