DSS 2.0 NO IDEA Avatar
  1. OMG Issue

DSS2 — Simplify representation of order and transportation types

Open Closed All
  • Key: DSS2-112
  • Legacy Issue Number: 5303
  • Status: closed  
  • Source: DMSO ( Michael Shadid)
  • Summary:

    The use of abstract valuetypes for order and transportation types in the
    current DistributedSimulation IDL require a user to have matching
    implementations of the handle and the handle factory for both the client
    federate and RTI. Since it is usually an RTI developer who provides the
    implementation of these types and their corresponding factories, it is
    unnecessary to use a valuetype to create this definition. It is
    recommended that the valuetype definitions for order and transportation
    types should be replaced with IDL interfaces for them and corresponding
    factory interfaces. The following revisions are recommended:
    On p. 1-12, in the first paragraph of the section headed “Message order
    and transportation types”, replace the words “(concrete) valuetype” with
    “IDL interface”.
    In the IDL, replace the valuetypes OrderType and TransportationType with
    the following:
    interface OrderType

    { boolean equals(in FederateHandle h); long hash_code(); string to_string(); long encoded_length(); Encoding encode(); };


    interface OrderTypeFactory { OrderType decode(in Encoding anEncoding); };


    interface TransportationType { boolean equals(in FederateHandle h); long hash_code(); string to_string(); long encoded_length(); Encoding encode(); }

    ;

    interface TransportationTypeFactory

    { TransportationType decode(in Encoding anEncoding); }

    ;
  • Reported: DSS 1.1 — Thu, 16 May 2002 04:00 GMT
  • Disposition: Resolved — DSS 2.0
  • Disposition Summary:

    see above
  • Updated: Fri, 6 Mar 2015 20:58 GMT