Hi,
Re: https://issues.jboss.org/browse/ISPN-694
We've got a little problem here. Paul requires that entries that might have
been expired while in the cache store, when loaded, we send expiration
notifications for them.
The problem is that expiration checking is currently done in the actual ca
On 2 May 2013, at 16:03, Galder Zamarreño wrote:
> Hi,
>
> Re: https://issues.jboss.org/browse/ISPN-694
>
> We've got a little problem here. Paul requires that entries that might have
> been expired while in the cache store, when loaded, we send expiration
> notifications for them.
>
> The p
Is it essential? No - but it would simplify things on my end.
If Infinispan can't implement expiration notifications, then I am forced
to use immortal cache entries and perform expiration myself. To do
this, I have to store meta information about the cache entry along with
my actual cache values,
On 3 May 2013, at 20:15, Paul Ferraro wrote:
> Is it essential? No - but it would simplify things on my end.
> If Infinispan can't implement expiration notifications, then I am forced
> to use immortal cache entries and perform expiration myself. To do
> this, I have to store meta information a
On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>
> On 3 May 2013, at 20:15, Paul Ferraro wrote:
>
>> Is it essential? No - but it would simplify things on my end.
>> If Infinispan can't implement expiration notifications, then I am forced
>> to use immortal cache entries and perform expirat
On Tue, May 21, 2013 at 6:07 PM, Galder Zamarreño wrote:
>
> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>
> >
> > On 3 May 2013, at 20:15, Paul Ferraro wrote:
> >
> >> Is it essential? No - but it would simplify things on my end.
> >> If Infinispan can't implement expiration notifications
On Tue, 2013-05-21 at 17:07 +0200, Galder Zamarreño wrote:
> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>
> >
> > On 3 May 2013, at 20:15, Paul Ferraro wrote:
> >
> >> Is it essential? No - but it would simplify things on my end.
> >> If Infinispan can't implement expiration notification
Sent from my iPhone
On 21 May 2013, at 16:07, Galder Zamarreño wrote:
>
> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>
>>
>> On 3 May 2013, at 20:15, Paul Ferraro wrote:
>>
>>> Is it essential? No - but it would simplify things on my end.
>>> If Infinispan can't implement expiratio
On May 21, 2013, at 5:11 PM, Dan Berindei wrote:
>
>
>
> On Tue, May 21, 2013 at 6:07 PM, Galder Zamarreño wrote:
>
> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>
> >
> > On 3 May 2013, at 20:15, Paul Ferraro wrote:
> >
> >> Is it essential? No - but it would simplify things on my
On May 21, 2013, at 7:42 PM, Paul Ferraro wrote:
> On Tue, 2013-05-21 at 17:07 +0200, Galder Zamarreño wrote:
>> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>>
>>>
>>> On 3 May 2013, at 20:15, Paul Ferraro wrote:
>>>
Is it essential? No - but it would simplify things on my end.
>>
On May 21, 2013, at 8:32 PM, Mircea Markus wrote:
>
>
> Sent from my iPhone
>
> On 21 May 2013, at 16:07, Galder Zamarreño wrote:
>
>>
>> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>>
>>>
>>> On 3 May 2013, at 20:15, Paul Ferraro wrote:
>>>
Is it essential? No - but it woul
On Wed, 2013-05-22 at 18:03 +0200, Galder Zamarreño wrote:
> On May 21, 2013, at 7:42 PM, Paul Ferraro wrote:
>
> > On Tue, 2013-05-21 at 17:07 +0200, Galder Zamarreño wrote:
> >> On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
> >>
> >>>
> >>> On 3 May 2013, at 20:15, Paul Ferraro wrote:
> >
On May 23, 2013, at 8:28 PM, Paul Ferraro wrote:
> On Wed, 2013-05-22 at 18:03 +0200, Galder Zamarreño wrote:
>> On May 21, 2013, at 7:42 PM, Paul Ferraro wrote:
>>
>>> On Tue, 2013-05-21 at 17:07 +0200, Galder Zamarreño wrote:
On May 6, 2013, at 2:20 PM, Mircea Markus wrote:
>
This notification feature seems to be very confusing, or at least I
find it awkward to understand all special conditions.
My doubt is, is it worth it?
Is there a reasonable use case, which works fine with all these limitations?
I'd rather drop support for such notifications rather than having to
On 28 May 2013, at 12:52, Sanne Grinovero wrote:
> This notification feature seems to be very confusing, or at least I
> find it awkward to understand all special conditions.
- we expire things at two levels: memory and store (CacheStore.purgeExpired)
- we cannot tell the existing store to perf
On 28 May 2013 13:02, Mircea Markus wrote:
>
> On 28 May 2013, at 12:52, Sanne Grinovero wrote:
>
>> This notification feature seems to be very confusing, or at least I
>> find it awkward to understand all special conditions.
>
> - we expire things at two levels: memory and store (CacheStore.purg
On May 28, 2013, at 1:52 PM, Sanne Grinovero wrote:
> This notification feature seems to be very confusing, or at least I
> find it awkward to understand all special conditions.
^ I agree, it's confusing and akward but you're mistaken in thinking that it's
a problem of the notification feature
17 matches
Mail list logo
