Announcement Announcement Module
Collapse
No announcement yet.
StatelessTicketCache timeToIdle...is it really timeToIdle Page Title Module
Move Remove Collapse
This topic is closed
X
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • StatelessTicketCache timeToIdle...is it really timeToIdle

    Ben,

    In the EhCacheBasedTicketCache there is only a property for minutesToIdle with a JavaDoc description that this is how long the item will remain in cache since its last access.

    However, this value is used for both timeToIdle and timeToLive in the EhCache. Therefore this effectively means that the property is timeToLive and not timeToIdle (or does EhCache do something special if they are the same?).

    Would it be possible to either be able to specify both values or rename the timeToIdle to timeToLive?

    We initially had some caching issues with this because we did not realize that it was really timeToLive and not timeToIdle so our clients were sending tickets they thought were still valid but really weren't.

    Thanks

  • #2
    Ben,

    I would also refactor EHCache based caches to use new Spring EHCache support to take advantage of configuring caches in Spring's DI environment.

    Comment


    • #3
      I would like to remove all Acegi Security provided EH-CACHEs in 0.7 and provide a new cache that integrates with Spring's new EH-CACHE services. We've already pre-warned this will happen in the reference documentation since 0.6.

      Scott, regarding your issue, please feel free to implement the changes locally until 0.7, or you could even write the new Spring integration cache and contribute it if you had unit tests.

      Comment

      Working...
      X