ng API in consistence with the thick client method and
> cacheConfiguration settings.
>
>
> From: Pavel Tupitsyn
> Sent: Saturday, October 19, 2019 9:20 PM
> To: dev
> Subject: Re: Thin clients: WithExpiryPolicy
>
> Alexandr,
>
> Sounds good to me.
>
> R
Sent: Saturday, October 19, 2019 9:20 PM
To: dev
Subject: Re: Thin clients: WithExpiryPolicy
Alexandr,
Sounds good to me.
Remaining question is - how do we serialize the expiry policy?
Thick client passes this to JNI as 3 int64 values (duration in
milliseconds).
But I don't think we need
upitsyn
> Sent: Friday, October 18, 2019 7:05 PM
> To: dev
> Subject: Re: Thin clients: WithExpiryPolicy
>
> Stateless approach looks a lot better to me.
>
> We have a choice:
> * Keep expiry policy on server and send an ID with every request (like a
> query cursor ID - 8
an expiration policy flag when
required.
Whenever the server sees that there is a request with expiration flag, we
deserialize a policy and apply it to the request.
From: Pavel Tupitsyn
Sent: Friday, October 18, 2019 7:05 PM
To: dev
Subject: Re: Thin clients: WithExpiryPolicy
Stateless approach
Stateless approach looks a lot better to me.
We have a choice:
* Keep expiry policy on server and send an ID with every request (like a
query cursor ID - 8 bytes)
* Send full expiry policy with every expiry-enabled request (24 bytes - or
maybe less? We should think about the format)
Stateful
Igniters,
I would like to add WithExpirePolicy support to thin clients. [1]
For a thick client, we can obtain a reference to a cache wrapper instance and
use cache API through it. At the same time, the thin client protocol is
stateless, we do not hold a reference to a cache but rather a cache
