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

Delete event #83

Closed
jirenius opened this issue May 2, 2019 · 1 comment
Closed

Delete event #83

jirenius opened this issue May 2, 2019 · 1 comment
Assignees
Labels
enhancement New feature or request

Comments

@jirenius
Copy link
Collaborator

jirenius commented May 2, 2019

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 that delete 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 types
  • when Resgate receives a delete event, it should delete the resource from the cache.
  • if the resource is not a query resource, or if there are no more query subscriptions, the resource should eventually be unsubscribe to NATS.
  • the event should be propagated further on to the client.
  • the client should not do anything. The resource will remain in the client's cache until unsubscribed.
@jirenius jirenius added the enhancement New feature or request label May 2, 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
jirenius added a commit that referenced this issue Oct 29, 2019
@jirenius jirenius self-assigned this Oct 29, 2019
@jirenius
Copy link
Collaborator Author

Resolved in #133

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

No branches or pull requests

1 participant