Closed copybara-service[bot] closed 2 years ago
Cache remote weak for multiple invocations.
The the first weak object is invalidated when it is sent across the process for the second time, due to 2 invalid cache:
a new EDOWeakObject is created with different remote address when remoteWeak is called.
remoteWeak
the old EDODeallocationTracker is released and invalidated the remote EDOObject cache when the second remote call is made.
Both of the above objects should be cached throughout the life time of the real object so that the remote process always use the same EDOObject.
Cache remote weak for multiple invocations.
The the first weak object is invalidated when it is sent across the process for the second time, due to 2 invalid cache:
a new EDOWeakObject is created with different remote address when
remoteWeakis called.the old EDODeallocationTracker is released and invalidated the remote EDOObject cache when the second remote call is made.
Both of the above objects should be cached throughout the life time of the real object so that the remote process always use the same EDOObject.