Request For Comments : Breaking change in SysCache config

k-dub · **Joined:** Thu May 12, 2005 8:45 am **Posts:** 226

As a follow-up to this thread http://nhibernate.sourceforge.net/forum/viewtopic.php?t=361, I want to change SysCache to use only one (1) expiration parameter.

The sliding expiration does not perform as any of us expected, and having a "static" expiration is not intuitive. I propose to have one property, say "expiration", that is X seconds in the future. The code would use a static expiration of DateTime.Now.AddSeconds( X ).

Thoughts?

cconstantin · **Joined:** Tue Oct 11, 2005 2:44 pm **Posts:** 12

I think you should leave the two parameters, but change the meaning of staticExpiration to a fixed amount of secconds since an object is added in the cache.

Can't wait for this to get done. If you need help, I volunteer. The change should be trivial though.

Regards,
Cris

martijnb · **Joined:** Sat May 14, 2005 8:40 am **Posts:** 130

The one (semi-static) expiration parameter would be perfect for my needs. But you might wait a little and see if someone has a good case for keeping the sliding expiration parameter.

KPixel · **Posted:** Sun Oct 16, 2005 7:44 am

IMO, as long as we can, we should keep the sliding expiration parameter. (remove it only if it is required...)

cconstantin · **Joined:** Tue Oct 11, 2005 2:44 pm **Posts:** 12

Have you guys done any progress on this? It would be a life saver. Again, if you have no time for it, I volunteer.

Thanks,
Cris

k-dub · **Joined:** Thu May 12, 2005 8:45 am **Posts:** 226

No one seemed to like my proposal, so I dropped it. Actually, I got busy and forgot about it.

I created a Jira issue for the slidingExpiration issue. http://jira.nhibernate.org/browse/NH-457

cconstantin · **Joined:** Tue Oct 11, 2005 2:44 pm **Posts:** 12

IMHO the new parameter is a must have.

Thanks,
Cris