Skip to content
This repository has been archived by the owner on Aug 8, 2023. It is now read-only.

Harden glyph loading #308

Closed
1 of 3 tasks
kkaefer opened this issue Jun 4, 2014 · 6 comments
Closed
1 of 3 tasks

Harden glyph loading #308

kkaefer opened this issue Jun 4, 2014 · 6 comments
Assignees

Comments

@kkaefer
Copy link
Contributor

kkaefer commented Jun 4, 2014

  • Make sure that we still draw a map, e.g. without labels, or with only some labels, if glyph PBFs fails to load. This likely requires implementing incremental parsing and updatable buckets (incremental parsing #163)
  • Cache glyph images indefinitely
  • Retry glyph loading when a request fails (e.g. due to shaky connection)
@hanchao
Copy link
Contributor

hanchao commented Jun 11, 2014

The glyphs load timed out some time, the tile will not render. Will you consider using the system font #260

[0x10bb5b458] exception [5/26/12]... failed: [ERROR] failed to load glyphs (-1): The request timed out.

@incanus
Copy link
Contributor

incanus commented Aug 25, 2014

Cache glyph images indefinitely

Will there ever be a need to expire these if they get updated somehow on the server. Seems unlikely but we may want to key on date / etag / some sort of version info just in case.

@jfirebaugh
Copy link
Contributor

We set a 10 day expiration for glyph PBFs on the new API endpoint.

@mikemorris
Copy link
Contributor

etag expiration could be nice to implement at some point, but 10day seems fine to launch.

@kkaefer
Copy link
Contributor Author

kkaefer commented Oct 29, 2014

We are doing etag expiration now.

@jfirebaugh
Copy link
Contributor

I don't think there's anything actionable here.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants