-
-
Notifications
You must be signed in to change notification settings - Fork 67
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
Delete event #83
Labels
enhancement
New feature or request
Comments
jirenius
added a commit
that referenced
this issue
Oct 28, 2019
jirenius
added a commit
that referenced
this issue
Oct 28, 2019
Added support for delete event to resgate. Added tests for delete event.
jirenius
added a commit
that referenced
this issue
Oct 28, 2019
jirenius
added a commit
that referenced
this issue
Oct 28, 2019
…rror. Added delete tests for query events.
Resolved in #133 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Story
The services need a way to tell Resgate that a resource has been deleted, and that it should no longer be served from the cache.
Solution
Expand the RES protocol to include support for a
delete
event. Since the protocol already states thatdelete
is a reserved event name, this change will not break backwards compatibility.Any subsequent client request for the resource should be handled the same way as for any other resource.
Notes
delete
events are valid for all resource typesdelete
event, it should delete the resource from the cache.The text was updated successfully, but these errors were encountered: