Closed
Bug 847679
Opened 12 years ago
Closed 10 years ago
Snuggle up against spaceheater
Categories
(Marketplace Graveyard :: Consumer Pages, defect, P3)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: cvan, Unassigned)
References
Details
(Keywords: perf, Whiteboard: [fireplace] p=3)
Spaceheater is the hosted version of Fireplace.
1. Django/Flask app calls any valid route (/, /app/<slug> /search, /settings, etc.)
2. The view reads the jinja template (aka nunjucks in Fireplace, the client-side packaged app version of the Marketplace) and extrapolates the various API calls needed.
3. Within the view we make the necessary HTTP requests to the API. And we pass back the responses as part of the context to the template.
4. Jinja compiles the template, and we send the resulting HTML down the wire.
This means that as a hosted app and as a web site, the user gets beautiful HTML on any synchronous page request. And with a capable user-agent (one supporting pushState, HTML5, etc.) any internal click from thereafter does JS magic to re-render the page.
Reporter | ||
Comment 1•12 years ago
|
||
Reminder: We need a settings file should contain the API urls and CDN. Also we need a build.py that contains the build IDs, like so:
BUILD_ID_CSS = "7076432"
BUILD_ID_JS = "7076432"
BUILD_ID_IMG = "7076432"
BUNDLE_HASHES = {'css:zamboni/files': '7f572d9', 'css:mkt/consumer-desktop': 'ec65c84', 'css:mkt/in-app-payments': '5709930', 'css:mkt/consumer': '3e484b4', 'css:zamboni/admin': '5fad975', 'css:mkt/stats': '2c6b37b', 'css:mkt/lookup': 'd858953', 'css:mkt/ecosystem': '9ad2023', 'css:mkt/devreg': '2abd377', 'css:zamboni/editors': 'b185ada', 'css:zamboni/impala': '53fcbdd', 'css:mkt/offline': '7d11131', 'css:zamboni/devhub': '7cc177a', 'css:mkt/splash': '598fe44', 'css:mkt/themes': 'a1c511d', 'css:mkt/
Updated•12 years ago
|
Priority: -- → P3
Whiteboard: [fireplace] → [fireplace] p=3
Comment 3•11 years ago
|
||
This is blocked on becoming a true packaged app because of the buchets. SH users will always see un-filtered results on first load (i.e.: not targeted to their device profile). That's less than ideal for FXOS/Android users. The only way around this is to add an intermediate redirect screen, but that defeats the purpose of having SH, anyway.
Once we're a packaged app, none of this will be an issue. Desktop users (and browser users...who cares) don't get quite-as-filtered results, so having them see potentially untargeted results on only the first load isn't such a sin.
Updated•11 years ago
|
Blocks: tarako-marketplace
Updated•11 years ago
|
No longer blocks: tarako-marketplace
Updated•10 years ago
|
Blocks: marketplace-perf
Comment 4•10 years ago
|
||
Do we think spaceheater is going to happen? Suggested that we close this tracker and bugs.
Updated•10 years ago
|
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•