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

Support memoization #18

Open
broneill opened this issue Jan 9, 2025 · 3 comments
Open

Support memoization #18

broneill opened this issue Jan 9, 2025 · 3 comments

Comments

@broneill
Copy link
Member

broneill commented Jan 9, 2025

Define a Memoized annotation which caches the result of a remote call on the client side. A memoized method which returns void also supports memoization.

When the remote object is disconnected, clear the cached results. If the annotation is declared as "sticky", then don't clear the cached results until the remote object is reconnected.

@broneill
Copy link
Member Author

broneill commented Jan 9, 2025

Should exceptions other than the declared remote exception be memoized too?

@broneill
Copy link
Member Author

broneill commented Jan 18, 2025

Consider adding a "proactive" option which calls the method when the remote object is transported, avoiding a remote call later.

@broneill
Copy link
Member Author

broneill commented Jan 26, 2025

I don't think the "proactive" option fits with this feature, considering that the method cannot accept parameters. Instead, define a separate Data annotation.

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

1 participant