/ doc / toc / ARCCore / Class / PropertyStreamLineWithOrigin

PropertyStreamLineWithOrigin

Edit keys at this level only

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

__TOCDet/Assembly = ARCCore
__TOCDet/Description = The rationale for this class is that -ReceiveAndDistribute- needs to distingush origin of data when routing it (in general, in order to avoid sending it back to its source).0x000D0x000A0x000D0x000AThis class is not to be confused with -PropertyStreamLine-.
__TOCDet/DocFragType = Class
__TOCDet/Name = PropertyStreamLineWithOrigin
__TOCDet/Namespace = ARCCore
__TOCDet/Type = PropertyStreamLineWithOrigin
__TOCDet/Attribute/AssemblyName = ARCCore
__TOCDet/Attribute/ClassNamespace = ARCCore
__TOCDet/Attribute/ClassType = PropertyStreamLineWithOrigin
__TOCDet/Attribute/Description = The rationale for this class is that -ReceiveAndDistribute- needs to distingush origin of data when routing it (in general, in order to avoid sending it back to its source).0x000D0x000A0x000D0x000AThis class is not to be confused with -PropertyStreamLine-.
DoNotAddTimestamp/__TOCDet/Assembly = ARCCore
DoNotAddTimestamp/__TOCDet/Description = Normally -StreamProcessor- inserts the required -Timestamp-s in the AgoRapide storage.0x000D0x000A0x000D0x000A-DoNotAddTimestamp- is a hack used when synchronizing an AgoRapide storage with other databases.0x000D0x000ANormally the synchronization is supposed to always be up-to-date, but at startup of the AgoRapide application some gap will naturally exist since the application was last shut down.0x000D0x000AThe initial synchronization at application startup can therefore utilize timestamp information from the source database, and signal through this property (DoNotAddTimestamp) that -StreamProcessor should NOT also insert timestamps itself (because the correct timestamps are much older).0x000D0x000A0x000D0x000ABeware that this is not an optimal solution because at application startup -StreamProcessor- will inevitably do some logging with up to date timestamps BEFORE synchronization starts, before older timestamps, meaning that timestamps in the AgoRapide storage (in the -PropertyStream-) are not sequential in rising order.0x000D0x000A0x000D0x000ATODO: An alternative would be to just inject the new properties directly in the data storage BEFORE -StreamProcessor- TODO: is initialized (storing text files directly into the data storage directory without knowledge of the -StreamProcessor-).0x000D0x000ATODO: BUT, if the actual synchronization status is stored within the data storage, we have a chicken-and-egg problem TODO: because then -StreamProcessor- would be needed in order to read the storage into memory TODO: BEFORE the synchronization takes place.0x000D0x000A
DoNotAddTimestamp/__TOCDet/DocFragType = ClassMember
DoNotAddTimestamp/__TOCDet/IsInherited = False
DoNotAddTimestamp/__TOCDet/IsInheritedDoc = False
DoNotAddTimestamp/__TOCDet/Lines = 11
DoNotAddTimestamp/__TOCDet/Name = DoNotAddTimestamp
DoNotAddTimestamp/__TOCDet/Namespace = ARCCore
DoNotAddTimestamp/__TOCDet/Type = PropertyStreamLineWithOrigin
DoNotAddTimestamp/__TOCDet/Attribute/DeclaringType = PropertyStreamLineWithOrigin
DoNotAddTimestamp/__TOCDet/Attribute/Description = Normally -StreamProcessor- inserts the required -Timestamp-s in the AgoRapide storage.0x000D0x000A0x000D0x000A-DoNotAddTimestamp- is a hack used when synchronizing an AgoRapide storage with other databases.0x000D0x000ANormally the synchronization is supposed to always be up-to-date, but at startup of the AgoRapide application some gap will naturally exist since the application was last shut down.0x000D0x000AThe initial synchronization at application startup can therefore utilize timestamp information from the source database, and signal through this property (DoNotAddTimestamp) that -StreamProcessor should NOT also insert timestamps itself (because the correct timestamps are much older).0x000D0x000A0x000D0x000ABeware that this is not an optimal solution because at application startup -StreamProcessor- will inevitably do some logging with up to date timestamps BEFORE synchronization starts, before older timestamps, meaning that timestamps in the AgoRapide storage (in the -PropertyStream-) are not sequential in rising order.0x000D0x000A0x000D0x000ATODO: An alternative would be to just inject the new properties directly in the data storage BEFORE -StreamProcessor- TODO: is initialized (storing text files directly into the data storage directory without knowledge of the -StreamProcessor-).0x000D0x000ATODO: BUT, if the actual synchronization status is stored within the data storage, we have a chicken-and-egg problem TODO: because then -StreamProcessor- would be needed in order to read the storage into memory TODO: BEFORE the synchronization takes place.0x000D0x000A
DoNotAddTimestamp/__TOCDet/Attribute/MethodName = DoNotAddTimestamp
DoNotAddTimestamp/__TOCDet/Attribute/MethodSignature = Boolean DoNotAddTimestamp
HasLocalOrigin/__TOCDet/Assembly = ARCCore
HasLocalOrigin/__TOCDet/Description = Locally generated data is not to be sent to -OutsideLocalReceiver-). We instead leave it to the 'outside' to decide if0x000D0x000A0x000D0x000Aeither0x000D0x000A0x000D0x000AA) Locally originated data should be put straight into the local 'outside' property store (typically an -PRich-)0x000D0x000ANOTE: This alternative, A), is dangerous because timestamps as generated by -AddTimestampAsRequired-0x000D0x000ANOTE: will not be sent to -OutsideLocalReceiver- in a deterministic manner compared to0x000D0x000ANOTE: when the data is pute into the 'outside' property store.0x000D0x000ANOTE: (in simpler words, the timestamp may come AFTER the data, leading to errors in parsing).0x000D0x000ANOTE: Use -SendToLocalReceiver- in order to escape this problem.0x000D0x000A0x000D0x000Aor0x000D0x000A0x000D0x000AB) We should wait until it gets returned back from the -CoreDB- through our subscription (and being sent to the local property store through -OutsideLocalReceiver-).0x000D0x000A0x000D0x000ASee also -SendToLocalReceiver- which can overrule this.0x000D0x000A
HasLocalOrigin/__TOCDet/DocFragType = ClassMember
HasLocalOrigin/__TOCDet/IsInherited = False
HasLocalOrigin/__TOCDet/IsInheritedDoc = False
HasLocalOrigin/__TOCDet/Lines = 17
HasLocalOrigin/__TOCDet/Name = HasLocalOrigin
HasLocalOrigin/__TOCDet/Namespace = ARCCore
HasLocalOrigin/__TOCDet/Type = PropertyStreamLineWithOrigin
HasLocalOrigin/__TOCDet/Attribute/DeclaringType = PropertyStreamLineWithOrigin
HasLocalOrigin/__TOCDet/Attribute/Description = Locally generated data is not to be sent to -OutsideLocalReceiver-). We instead leave it to the 'outside' to decide if0x000D0x000A0x000D0x000Aeither0x000D0x000A0x000D0x000AA) Locally originated data should be put straight into the local 'outside' property store (typically an -PRich-)0x000D0x000ANOTE: This alternative, A), is dangerous because timestamps as generated by -AddTimestampAsRequired-0x000D0x000ANOTE: will not be sent to -OutsideLocalReceiver- in a deterministic manner compared to0x000D0x000ANOTE: when the data is pute into the 'outside' property store.0x000D0x000ANOTE: (in simpler words, the timestamp may come AFTER the data, leading to errors in parsing).0x000D0x000ANOTE: Use -SendToLocalReceiver- in order to escape this problem.0x000D0x000A0x000D0x000Aor0x000D0x000A0x000D0x000AB) We should wait until it gets returned back from the -CoreDB- through our subscription (and being sent to the local property store through -OutsideLocalReceiver-).0x000D0x000A0x000D0x000ASee also -SendToLocalReceiver- which can overrule this.0x000D0x000A
HasLocalOrigin/__TOCDet/Attribute/MethodName = HasLocalOrigin
HasLocalOrigin/__TOCDet/Attribute/MethodSignature = Boolean HasLocalOrigin
ReceivedFromOutgoing/__TOCDet/Assembly = ARCCore
ReceivedFromOutgoing/__TOCDet/Description = Data received from an outgoing connection, that is, data received based on 'this' application's subscription request (as subscribing client).0x000D0x000AThis data must NOT be sent back again over any outgoing connection.0x000D0x000AIt should only be distributed locally (through -OutsideLocalReceiver, typical for an -Client-) and to incoming connections (incoming connections from subscribing clients) whenever it matches their -Subscription- request (typical for an -ArmDB-
ReceivedFromOutgoing/__TOCDet/DocFragType = ClassMember
ReceivedFromOutgoing/__TOCDet/IsInherited = False
ReceivedFromOutgoing/__TOCDet/IsInheritedDoc = False
ReceivedFromOutgoing/__TOCDet/Lines = 3
ReceivedFromOutgoing/__TOCDet/Name = ReceivedFromOutgoing
ReceivedFromOutgoing/__TOCDet/Namespace = ARCCore
ReceivedFromOutgoing/__TOCDet/Type = PropertyStreamLineWithOrigin
ReceivedFromOutgoing/__TOCDet/Attribute/DeclaringType = PropertyStreamLineWithOrigin
ReceivedFromOutgoing/__TOCDet/Attribute/Description = Data received from an outgoing connection, that is, data received based on 'this' application's subscription request (as subscribing client).0x000D0x000AThis data must NOT be sent back again over any outgoing connection.0x000D0x000AIt should only be distributed locally (through -OutsideLocalReceiver, typical for an -Client-) and to incoming connections (incoming connections from subscribing clients) whenever it matches their -Subscription- request (typical for an -ArmDB-
ReceivedFromOutgoing/__TOCDet/Attribute/MethodName = ReceivedFromOutgoing
ReceivedFromOutgoing/__TOCDet/Attribute/MethodSignature = Boolean ReceivedFromOutgoing
SendToLocalReceiver/__TOCDet/Assembly = ARCCore
SendToLocalReceiver/__TOCDet/Description = Means 'send to local receiver regardless of origin'.0x000D0x000A0x000D0x000ASee -HasLocalOrigin- for explanation.
SendToLocalReceiver/__TOCDet/DocFragType = ClassMember
SendToLocalReceiver/__TOCDet/IsInherited = False
SendToLocalReceiver/__TOCDet/IsInheritedDoc = False
SendToLocalReceiver/__TOCDet/Lines = 3
SendToLocalReceiver/__TOCDet/Name = SendToLocalReceiver
SendToLocalReceiver/__TOCDet/Namespace = ARCCore
SendToLocalReceiver/__TOCDet/Type = PropertyStreamLineWithOrigin
SendToLocalReceiver/__TOCDet/Attribute/DeclaringType = PropertyStreamLineWithOrigin
SendToLocalReceiver/__TOCDet/Attribute/Description = Means 'send to local receiver regardless of origin'.0x000D0x000A0x000D0x000ASee -HasLocalOrigin- for explanation.
SendToLocalReceiver/__TOCDet/Attribute/MethodName = SendToLocalReceiver
SendToLocalReceiver/__TOCDet/Attribute/MethodSignature = Boolean SendToLocalReceiver

Edit single sub keys only: __TOCDet / DoNotAddTimestamp / HasLocalOrigin / ReceivedFromOutgoing / SendToLocalReceiver

Generated 2025-04-28 16:00:00.905 UTC