From d510aaffe5981964d69855b58d894de76f69bcaa Mon Sep 17 00:00:00 2001
From: Axel Uhl <axel.uhl@sap.com>
Date: Sun, 8 Jul 2018 23:10:12 +0200
Subject: [PATCH] added a comment

Change-Id: I064852e27210946caafd3efbf61645b539bced4b
---
 .../com/sap/sailing/domain/tracking/impl/TimeRangeCache.java    | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/java/com.sap.sailing.domain.shared.android/src/com/sap/sailing/domain/tracking/impl/TimeRangeCache.java b/java/com.sap.sailing.domain.shared.android/src/com/sap/sailing/domain/tracking/impl/TimeRangeCache.java
index de43e8d22f7..b4ed5ace655 100755
--- a/java/com.sap.sailing.domain.shared.android/src/com/sap/sailing/domain/tracking/impl/TimeRangeCache.java
+++ b/java/com.sap.sailing.domain.shared.android/src/com/sap/sailing/domain/tracking/impl/TimeRangeCache.java
@@ -144,7 +144,7 @@ public class TimeRangeCache<T> {
             // no writer can be active because we're holding the read lock; read access on the lruCache is synchronized using
             // the lruCache's mutex; this is necessary because we're using access-based LRU pinging where even getting an entry
             // modifies the internal parts of the data structure which is not thread safe.
-            synchronized (lruCache) {
+            synchronized (lruCache) { // ping the "perfect match" although it may not even have existed in the cache
                 lruCache.get(new Util.Pair<TimePoint, TimePoint>(from, to));
             }
             return result;