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

Cache Expiry Pushing #17

Open
PaymonK opened this issue Mar 7, 2018 · 1 comment
Open

Cache Expiry Pushing #17

PaymonK opened this issue Mar 7, 2018 · 1 comment
Assignees

Comments

@PaymonK
Copy link
Contributor

PaymonK commented Mar 7, 2018

Cache Expiry Pushing

ApiProxyGenerator: If the method takes no parameters, and defines PushExpireClientCache, then in the generated XXXApi class, in a static constructor, register a SignalR or Socket client tot he server to receive cache expiry notifications.

On the server side, we need to add a static AsyncEvent object on the appropriate entity type, which is used as the signal point.
public static AsyncEvent PeopleDataChanged;

In the Api controller class, in a static constructor, add:
PushExpireClientCache.For(nameof(All)).PushUpon(Person.PeopleDataChanged);

Internally that shall implement a mechanism to host the SignalR stuff. So that every time the event is raised, the remote client sockets receive a signal to expire their cache.

@stale
Copy link

stale bot commented Dec 10, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the wontfix label Dec 10, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants