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

Caching vs WMS #48

Open
NyakudyaA opened this issue Jan 24, 2020 · 3 comments
Open

Caching vs WMS #48

NyakudyaA opened this issue Jan 24, 2020 · 3 comments
Assignees

Comments

@NyakudyaA
Copy link
Contributor

Problem

Some tile rendering takes place, we are using WMS to retrieve new data. Can we use gwc for all layers?

Solution

If we add &tiled=true to all our request we will automatically cache all the layers. This seems to also work with wms filters.

We need to test out the following.

@NyakudyaA NyakudyaA self-assigned this Jan 24, 2020
@lucernae lucernae mentioned this issue Feb 24, 2020
@lucernae
Copy link
Contributor

The endpoint we use in the front end is using original WMS.
I switch it to use GWC endpoint per your suggestions in this PR #75 .
I also added tiled: true options for WMS filters.

@lucernae
Copy link
Contributor

@NyakudyaA I'm not familiar with caching, but for layers that we use with cql_filter, how do we cache it?
If we are using different flood_event_id than GWC should return different tiles, but is this configuration possible?

@NyakudyaA
Copy link
Contributor Author

@NyakudyaA I'm not familiar with caching, but for layers that we use with cql_filter, how do we cache it?
If we are using different flood_event_id than GWC should return different tiles, but is this configuration possible?

@lucernae we might have to test that but from my understanding if a request is passed to geoserver it will go through wms for the first time and then gets cached. So if a request is executed the second time it already exist and will come from gwc. If we are using the same bounding box and different filter we need to check if the logic is working properly

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

No branches or pull requests

2 participants