Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better object caching #80

Open
dlareau opened this issue Jan 14, 2019 · 2 comments
Open

Better object caching #80

dlareau opened this issue Jan 14, 2019 · 2 comments
Labels
enhancement Hard Hard to implement Long term For systematic issues that won't be fixed in just one release.

Comments

@dlareau
Copy link
Owner

dlareau commented Jan 14, 2019

This is issue 1/3 spawned from the closing of #11.
The server right now does nothing except the default database query caching, which is becoming not enough.

The server should work alongside a caching framework such as memcached to store user sessions, commonly accessed objects (like the current hunt, team, and puzzle data), and other various things.

@dlareau dlareau added enhancement Hard Hard to implement labels Jan 14, 2019
@dlareau dlareau added the Long term For systematic issues that won't be fixed in just one release. label Feb 8, 2019
@dlareau
Copy link
Owner Author

dlareau commented Feb 9, 2019

Thought: Consider divorcing re-usable content from individual content on most pages. The overall pages would be cached and any individualism (previous answers, which puzzles are solved) would be loaded in a separate ajax request after the initial page loads.

@dlareau
Copy link
Owner Author

dlareau commented Feb 9, 2019

If this can work, consider also somehow doing this for the navbar, which is the only thing stopping most pages from being cached for logged in users.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement Hard Hard to implement Long term For systematic issues that won't be fixed in just one release.
Projects
None yet
Development

No branches or pull requests

1 participant