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

Write up LDF Cache Clearing Problem #27

Closed
no-reply opened this issue Jan 7, 2017 · 3 comments
Closed

Write up LDF Cache Clearing Problem #27

no-reply opened this issue Jan 7, 2017 · 3 comments
Assignees
Labels
Milestone

Comments

@no-reply
Copy link
Collaborator

no-reply commented Jan 7, 2017

The ActiveTriples::LinkedDataFragments implementation doesn't provide a way to clear individual resources from the cache. This makes invalidation hard. It's not obvious how to handle this in the current implementation.

This ticket is to get a more complete write-up of the problems into an issue on the LDF repository and raise it for discussion in the Applied Linked Data WG.

@no-reply no-reply added this to the One milestone Jan 7, 2017
@no-reply no-reply self-assigned this Jan 7, 2017
@hackartisan
Copy link

hackartisan commented Jan 10, 2017

I think this is related to the work Lynette has been doing to define / configure cache expiration behavior. See her branch of Linked Data Fragments https://github.com/ActiveTriples/linked-data-fragments/tree/cache_config/config

working stemming from this issue ActiveTriples/linked-data-fragments#31 and follow-up discussions on applied linked data group.

@no-reply
Copy link
Collaborator Author

Engaging with the discussion on ActiveTriples/linked-data-fragments#31 seems like the right move. I think I can write up a proposal based on what's discussed there already.

@no-reply
Copy link
Collaborator Author

no-reply commented Feb 5, 2017

Approaches for cache control:

In any of these three cases, questions that need to be answered include:

  • What are the pre-warming needs?
    • Do search needs for an authority require a full pre-load of that authority?
    • Or can search be dependant on an external service?
  • What happens when the cache "invalidates"?
    • do we clear data from the backend,
    • or simply require re-fetch on the next retrieval if the remote is available?
  • What is an acceptable TTL?
  • Does the client ever need to manually invalidate the cache?

I think that's the general shape of the problem.

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

No branches or pull requests

2 participants