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

wfs-service: use a no-op LayerGroupContainmentCache #468

Closed

Conversation

groldan
Copy link
Member

@groldan groldan commented May 14, 2024

The wfs-service contributes a no-op LayerGroupContainmentCache to avoid the runtime overhead of building up the cache at startup, and the unnecessary memory footprint.

LayerGroupContainmentCache is a securtity subsystem aid and WFS does not deal with LayerGroupInfo at all.

@groldan groldan added the enhancement New feature or request label May 14, 2024
@groldan groldan marked this pull request as draft May 14, 2024 03:06
@groldan groldan force-pushed the wfs/noop-layergroupcontainmentcache branch 3 times, most recently from 83061a5 to 468089a Compare May 14, 2024 03:32
groldan added 2 commits May 14, 2024 19:27
The wfs-service contributes a no-op `LayerGroupContainmentCache` to
avoid the runtime overhead of building up the cache at startup, and the
unnecessary memory footprint.

`LayerGroupContainmentCache` is a securtity subsystem aid and WFS does not
deal with `LayerGroupInfo` at all.
@groldan groldan force-pushed the wfs/noop-layergroupcontainmentcache branch from 468089a to 6483a04 Compare May 14, 2024 22:42
@groldan groldan closed this May 14, 2024
@groldan groldan deleted the wfs/noop-layergroupcontainmentcache branch May 14, 2024 22:43
@groldan
Copy link
Member Author

groldan commented May 14, 2024

Superseded by #469

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant