You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 5, 2022. It is now read-only.
We have used tailor for serving multiple fragments and among them some fragments are used in all the page like header, footer, navigation etc.
Now I want to stop to reload this header, footer and navigation fragments in different application route.
Do we have any functionality to stop reload this fixed fragments.
The text was updated successfully, but these errors were encountered:
It is all about new framework and for now it is not possible to integrate ilc in our existing architecture. So if Tailor does not have any option to do this so we need to implement client caching.
Please suggest me if we have any option in tailor to prevent this behavior.
Can you get in to more specific details? Do you want to server cached assets for the fragments on reload or you don't want the request itself to be fired for those fragments?
Both of that scenarios are not baked in to tailor, so you might want to extend the requestFragment function to do caching on either tailor level or you can add support for client side caching.
Actually I want to stop to request itself from browser to server as well.
Can you please some idea how we can handle client side caching using requestFragment.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have used tailor for serving multiple fragments and among them some fragments are used in all the page like header, footer, navigation etc.
Now I want to stop to reload this header, footer and navigation fragments in different application route.
Do we have any functionality to stop reload this fixed fragments.
The text was updated successfully, but these errors were encountered: