- Fix
max-age
math (seconds vs. ms). (@leonardehrenfried)
- Typo fix.
- Respect
max-age
inCache-Control
header. - Upgrade
tilelive-streaming
.
- Prevent lock leakage when cache entries already exist.
- Pass upstream errors forward and skip the cache
- Rely on
TileStream
's (tilelive-streaming
) error handler to prevent non- fatal errors from bubbling up and terminating Node.
- Attach an error handler to prevent
getTile
failures from terminating Node.
- Flip
setImmediate
queuing of source closure so that sources are removed as early as possible.
- Upgrade to
[email protected]
with improved handling of empty tiles.
- Remove
close()
d sources from the cache. - Eliminate
closeDelay
as removal of closed sources addresses the same issue more cleanly.
- Fix cache handling for items w/o
.length
(@petrsloup)
- Update
tilelive-streaming
to v0.5.1
tilelive-streaming
-powered proactive metatile caching.
- Don't modify URLs;
?cache=true
was previously being appended. It will continue to be respected if provided.
- Reduce the size of the repeated URI sub-key to limit memory pressure.
- Hash cache keys to avoid excessive memory use (notable when
uri.xml
is present)
- Default
uri.query.cache
totrue
- Fully normalize URIs so string and object forms match.
- Handle
options
better (especially when keys are present withundefined
values).
- Add
options.closeDelay
- Don't cache when source URIs contain
?cache=false
- Allow cache size to be set to
0
- Handle sources without
{getGrid,getTile,getInfo}
methods
- Depend on the correct version of
locking-cache
- Include callback properties in cache keys
- Don't re-wrap sources that have already been cache-enabled
- Use
JSON.stringify()
everywhere.
- Upgrade
locking-cache
to 0.1.2 - Make the source cache size configurable via
options.sources
(and default it to 6). - Fix
dispose()
implementation to matchlocking-cache
's behavior. - Use
JSON.stringify()
to generate keys, asurl.format()
drops unrecognized / overloaded properties.
- Initial released version