You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ibatis.apache.org by "tom liu (JIRA)" <ib...@incubator.apache.org> on 2008/12/20 02:16:46 UTC

[jira] Created: (IBATISNET-288) There should be a feature to set timeout on Caching Object. Do not always flush all objects.

There should be a feature to set timeout on Caching Object. Do not always flush all objects.
--------------------------------------------------------------------------------------------

                 Key: IBATISNET-288
                 URL: https://issues.apache.org/jira/browse/IBATISNET-288
             Project: iBatis for .NET
          Issue Type: Wish
          Components: DataMapper
    Affects Versions: DataMapper 1.6.2
         Environment: .net 2.0/vs2005
            Reporter: tom liu


On CacheModels, there is a feature to flush all objects, when ticks are greater then flushInterval. But sometimes, we should have a new feature to set one object dirty; flushing all Objects will be heavy.
i think there would be a new feature TimeOut that like FlushInterval: when one object in caches timeout is greater than timeoutInterval, then set the object dirty, so app will be got a null.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.