Skip to content
This repository has been archived by the owner on Dec 5, 2022. It is now read-only.

Stop to reload fixed fragments in different route for application. #331

Open
Pragnesh-Er2007 opened this issue Jul 27, 2020 · 4 comments
Open

Comments

@Pragnesh-Er2007
Copy link

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.

@StyleT
Copy link

StyleT commented Jul 27, 2020

Hi!
I believe you can look at the https://github.com/namecheap/ilc It allows you to do this & it's based on Tailor.

@Pragnesh-Er2007
Copy link
Author

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.

@vigneshshanmugam
Copy link
Collaborator

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.

@Pragnesh-Er2007
Copy link
Author

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 free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants