-
Notifications
You must be signed in to change notification settings - Fork 3
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
feature_request: return wrapped cached object on which methods of cached object can be directly called, and executed in server #13
Comments
Hey @tkmmark , sorry for the late response, finally have some time to look at this properly. This looks pretty good to me! Actually would you mind to submit this part of code as a PR to compas_cloud ? I'm sure this will be a very useful feature |
Yes, and thanks for asking earlier on slack as well. |
don't use ABC's on the client side because they create memory leaks in ironpython... |
@tkmmark Please follow up with the pull request, if still relevant. |
I will follow up with Li Chen, |
Create a easy-to-work with wrapped cached object on which methods of the cached object (which may call all the nice scientific libraries we cannot use in IronPython) can be directly called--triggering their execution in the server.
An example of how it would be used from the point of the Proxy-using developer:
This involves creating a wrapped cached object that gets returned when Proxy.cache(object) is used:
This class, as can be seen, gathers and wrap all the methods that are in the cached object's class, so that they may directly be called from the Client side...
Where proxy.run_method_of_cached was discussed in an earlier Issue...
Finally, the wrapped object also provides a handy restore function that allows the cached object to be recreated in the client side.
The text was updated successfully, but these errors were encountered: