always returns false for "known" output parameter #162

strk opened this Issue Feb 26, 2014 · 1 comment


None yet
1 participant

strk commented Feb 26, 2014

Theoretically the function should return an indication of whether the saved value was already known or not. This is currently failing with "false" always being the return.

As a consequence, the layergroups are considered new more than they should.
The only reason why they are not is because of a second-level internal LRU cache,
see #160

@strk strk added this to the 0.19.1 milestone Feb 26, 2014

@strk strk added bug labels Feb 26, 2014


strk commented Feb 26, 2014

Affects performance because in a clustered environment each process will check new coming POSTs over and over.

@strk strk closed this in b5b823b Feb 26, 2014

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment