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

Add template pre-evaluation #13

Open
robertotru opened this issue Dec 12, 2016 · 2 comments
Open

Add template pre-evaluation #13

robertotru opened this issue Dec 12, 2016 · 2 comments

Comments

@robertotru
Copy link
Member

Currently the email with template are scheduled and compiled through the template engine when they need to be sent. However, this may affect the response time when thousands email need to be executed simultaneously.
Therefore, it could be a good idea to start compiling the templates in advance when the burden is lower.

@robertotru robertotru changed the title Add Persistence Add template pre-evaluation Dec 12, 2016
@robertotru robertotru added this to the Long-term goals and ideas milestone Dec 12, 2016
@msauza
Copy link

msauza commented Mar 9, 2017

Template pre-evaluation depends on every used engine, e. g. freemarker has template cache by default. If all engines implements the same mechanism, maybe on bean could process templates post-init.

Meanwhile using freemarker ensure that template loading and evaluation happen once until it got modified.

@robertotru
Copy link
Member Author

I mean. What if a template is conveted to html immediately when the machine burden is low or there is available computer power? One could save some time and memory: a big String instead of storing the template plus model object. Anyway I am still not sure about this story.

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

No branches or pull requests

2 participants