-
Key: DDSRPC_-9
-
Status: closed
-
Source: Real-Time Innovations ( Sumant Tambe)
-
Summary:
Section 8.3.1.2
What about collisions in the implied IDL types, hashes, etc. If a collision appears what are the rules to follow, because client and service could be developed by independent groups and DDS vendors which should than follow the same rulesWhat when the user has an interface with a user defined parameter with the name return_ and there is a return value? This leads to a clash in the generated struct
What when the user has an operation remoteEx in his interface IDL?
What if there is a clash between the const hash name and user defined IDL?
What is the behavior of @autoid with a hash-collision? Also what happens when operations are reordered at the moment there is a hash-collision? Couldn't that break interoperability?
-
Reported: DDS-RPC 1.0b1 — Wed, 4 Nov 2015 23:54 GMT
-
Disposition: Resolved — DDS-RPC 1.0
-
Disposition Summary:
Collision resolutions incorporated in multiple sections
The following collision resolution techniques have been incorporated
-
Updated: Tue, 12 Jul 2016 14:44 GMT