I just noticed something I've never seen before, and I've opened a new tab to preserve it while I type this.

The first time I refreshed my PM tab this morning, the nodlets told me that the xp fairly had been, that there had been a change to my xp overnight, the time was 7:43:10Z and I had one reply.

So I clicked on the reply.

When the reply was displayed, the time shown was 7::43:22Z, but the contents of the xp nodelet continued to inform me of the same information as on the previous scree, including the xp change which normally disappears after the first refresh.

If it is just a quirk of the caching, then no harm done. But if it is accidentally being re-queried/calculated, then it could be costly to PM.

So, no harm, no foul, but something changed,I noticed, ... this post.

With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?
  • Comment on Has PM caching strategy changed (for the better)?

Back to Perl Monks Discussion