The runtime flag Datex.Runtime.OPTIONS.PROTECT_POINTERS should be set to true per default.
Ideally, this is not a breaking change.
Remote pointers returned from a function call on the remote endpoint or directly sent from the remote endpoint can still be accessed like before - pointer access permissions are managed automatically in most cases.
We just need to make sure there are no edge cases left.
Todo:
[x] Get Hydration to work with protected pointers (UIX)
[ ] Check if anything else breaks in UIX with protected pointers enabled
[ ] Enable protected pointers in all our internal applications and make sure they still work correctly
[ ] Make sure the pointer protection rules can't be bypassed somehow
The runtime flag
Datex.Runtime.OPTIONS.PROTECT_POINTERSshould be set totrueper default. Ideally, this is not a breaking change. Remote pointers returned from a function call on the remote endpoint or directly sent from the remote endpoint can still be accessed like before - pointer access permissions are managed automatically in most cases. We just need to make sure there are no edge cases left.Todo: