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.

Sign up for GitHub

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

Jump to bottom

Investigate caching of primary navigation DOM #127

Open
JimKerslake opened this issue May 15, 2024 · 0 comments
Open

Investigate caching of primary navigation DOM #127

JimKerslake opened this issue May 15, 2024 · 0 comments

Comments

@JimKerslake
Copy link
Collaborator

As a possible performance enhancement, we could try to memory-cache the rendered DOM for the primary navigation... to be used only by unauthenticated users since otherwise each individual user session would need its own cached version (since visibility of nav nodes depends on so many user-specific things).
JimKerslake added a commit that referenced this issue May 17, 2024
@JimKerslake
#127 experimental caching nav view component
e146c64
JimKerslake added a commit that referenced this issue May 17, 2024
@JimKerslake
Merge pull request #128 from cloudscribe/feature/127
01a086c 
#127 caching nav view component
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@JimKerslake