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

Store assets given by the client and return them along with the predicted page #22

Closed
dnesteryuk opened this issue Jan 4, 2017 · 1 comment
Milestone

Comments

@dnesteryuk
Copy link
Collaborator

@dnesteryuk dnesteryuk commented Jan 4, 2017

The client will send a list of assets for each being tracked page. That list of assets should be stored per page node. Once the prediction is made, the engine should return a list of assets of the predicted page along with the path.

@dnesteryuk dnesteryuk changed the title Prefetching assets Store assets given by the client and return them along with the predicted page Jul 20, 2017
@dnesteryuk dnesteryuk added this to the 0.2 milestone Jul 20, 2017
dnesteryuk added a commit that referenced this issue Sep 12, 2017
Now the engine accepts a list of assets of a page. That list gets
stored along with the path of the page. Once the prediction is made,
the path and assets of a predicted page gets returned in the response.
So, the client can instruct browsers to prefetch the predicted page and
assets of it.

Since the engine needs to work with the more complex structure of data,
it got altered to accept requests in the json format and respond
in this format too. In particular, we could use a pure POST request,
but the decision was made to use the same format for requests
and responses in order to be consistent.
@dnesteryuk
Copy link
Collaborator Author

@dnesteryuk dnesteryuk commented Sep 12, 2017

Implemented in the attached commit.

@dnesteryuk dnesteryuk closed this Sep 12, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant