- May 01, 2020
-
-
George Kiagiadakis authored
-
- Apr 21, 2020
-
-
George Kiagiadakis authored
+ add the useful _find_proxy() method
-
- Mar 31, 2020
-
-
George Kiagiadakis authored
-
- Feb 19, 2020
-
-
George Kiagiadakis authored
-
- Feb 14, 2020
-
-
George Kiagiadakis authored
There are 3 kinds of WpProxy objects: * the ones that are created as a result of binding a global from the registry * the ones that are created as a result of calling into a remote factory (wp_node_new_from_factory, etc...) * the ones that are a local implementation of an object (WpImplNode, etc...) and are exported Previously the object manager was only able to track the first kind. With these changes we can now also have globals associated with WpProxies that were created earlier (and caused the creation of the global). This saves some resources and reduces round-trips (in case client code wants to change properties of an object that is locally implemented, it shouldn't need to do a round-trip through the server)
-
- Feb 12, 2020
-
-
George Kiagiadakis authored
-
- Jan 16, 2020
-
-
George Kiagiadakis authored
-
- Jan 13, 2020
-
-
Julian Bouzas authored
-
- Nov 13, 2019
-
-
George Kiagiadakis authored
-