[ 
https://issues.apache.org/jira/browse/GEODE-3392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16253593#comment-16253593
 ] 

ASF GitHub Bot commented on GEODE-3392:
---------------------------------------

dgkimura commented on a change in pull request #150: GEODE-3392: Converts 
CacheStatistics to std::chrono.
URL: https://github.com/apache/geode-native/pull/150#discussion_r151152356
 
 

 ##########
 File path: cppcache/src/ExpiryTaskManager.cpp
 ##########
 @@ -61,20 +61,6 @@ long 
ExpiryTaskManager::scheduleExpiryTask(ACE_Event_Handler* handler,
   return m_reactor->schedule_timer(handler, 0, expTimeValue, intervalValue);
 }
 
-long ExpiryTaskManager::scheduleExpiryTask(
 
 Review comment:
   I thought we were trying to get rid of the other scheduleExpiryTask above 
that took `uint32_t`?

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


> Migrate CacheStatistics to use std::chrono
> ------------------------------------------
>
>                 Key: GEODE-3392
>                 URL: https://issues.apache.org/jira/browse/GEODE-3392
>             Project: Geode
>          Issue Type: Improvement
>          Components: native client
>            Reporter: Ernest Burghardt
>
>  virtual std::chrono::time_point getLastModifiedTime() const;
>   /**
>    * For an entry, returns the last time it was accessed via
>    * @see Region::get
>    * @see getLastModifiedTime
>    */
>   virtual std::chrono::time_point getLastAccessedTime() const;
>  private:
>   virtual void setLastAccessedTime(std::chrono::time_point lat);
>   virtual void setLastModifiedTime(std::chrono::time_point lmt);
>   std::atomic<std::chrono::time_point> m_lastAccessTime;
>   std::atomic<std::chrono::time_point> m_lastModifiedTime;



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Reply via email to