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

Mark the server side as done #6

Open
pupeno opened this Issue Sep 23, 2015 · 2 comments

Comments

Projects
None yet
2 participants
@pupeno
Owner

pupeno commented Sep 23, 2015

It would be easy to have NodeJS listening on an async.core channel for a "we are done" message to trigger early termination of pre-rendering and thus shipping of the page to the user.

What I'm not sure if it'll be easy or even possible is to have the application send that message.

@oborder

This comment has been minimized.

oborder commented Dec 12, 2015

Hi

This is hypothetical and is based on the way I structure my apps. It is similar to what I have seen from other people, and as far as I can tell to your example in ninjatools...

For some applications it would not be hard to dispatch message [:data-ready ...] for each page after all the data is fetched for the page. This could be used to short circuit waiting for timeout. After all the data is ready we just need to wait for render once more (maybe reagent force-update-all would help?)

@pupeno

This comment has been minimized.

Owner

pupeno commented Dec 13, 2015

Yes, that is correct. My plan is to have a series of heuristics and you can mix and match according to your app, timeout being the fallback. You can have an event trigger the end, you can have the lack of queue events (plus pending ajax requests) trigger the end, etc.

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