You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, an endpoint preemptively attaches pointer values to a DATEX message if a few conditions are met
The pointer action type is GET (not SET or INIT)
The DATEX message is not sent to the its own instance
The receiving endpoint is not yet a subscriber of the pointer
The current endpoint is the owner of the pointer
Are there any more constraints we need to add? Can we remove some?
I am not so sure if we need 4). If the receiver endpoint trusts the sender, it can also intialize a foreign pointer with a preemptive values provided by the sender (which is not the owner of the pointer).
Currently, with 4), we loose the ability to preemptively load pointers e.g. when the backend endpoint of a UIX app changes, but the pointers still have the previous backend endpoint as an origin (yes, this is an edge case, because normally you should never change the endpoint on the backend)
This discussion was converted from issue #50 on January 19, 2024 12:02.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Currently, an endpoint preemptively attaches pointer values to a DATEX message if a few conditions are met
GET
(notSET
orINIT
)Are there any more constraints we need to add? Can we remove some?
I am not so sure if we need 4). If the receiver endpoint trusts the sender, it can also intialize a foreign pointer with a preemptive values provided by the sender (which is not the owner of the pointer).
Currently, with 4), we loose the ability to preemptively load pointers e.g. when the backend endpoint of a UIX app changes, but the pointers still have the previous backend endpoint as an origin (yes, this is an edge case, because normally you should never change the endpoint on the backend)
Beta Was this translation helpful? Give feedback.
All reactions