CERTI - Tasks: task #9306, Change Order Type
You are not allowed to post comments on this tracker with your current authentication level.
task #9306: Change Order Type
Submitter: | Pierre Siron <siron> | ||
Submitted: | Tue 07 Apr 2009 11:29:19 AM UTC | ||
Should Start On: | Tue 07 Apr 2009 12:00:00 AM UTC | Should be Finished on: | Sun 07 Jun 2009 12:00:00 AM UTC |
Category: | None | Priority: | 3 - Low |
Status: | None | Privacy: | Public |
Assigned to: | siron | Percent Complete: | 0% |
Open/Closed: | Open | Planned Release: | None |
RTI Service Groups: | None |
Wed 08 Apr 2009 11:07:43 AM UTC, comment #1: |
Eric NOULARD <erk> |
Tue 07 Apr 2009 11:29:19 AM UTC, original submission:
Implementation of 2 services (time management) :
|
Pierre Siron <siron> |
No files currently attached
Depends on the following items: None found
Items that depend on this one: None found
There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.
Powered by Savane 3.13-f8d8.
Corresponding source code
The definition of the RECEIVE and TIMESTAMP
symbolic value in certi.hh is not so strange
it is used in several places in the code:
RTIA/RTIA_network.cc
libCERTI/GAV.cc
libRTI/RTITypesImp.cc
and in the parser/lexer for Fed File.
However the USER should NEVER use those definition
(in fact the symbolic definition should be made private
to libCERTI I think).
The user should use the RTIambassador API
OrderingHandle getOrderingHandle(const char *)
in order to retrieve a proper value for
OrderingHandle.
This value may then be used in
changeAttributeOrderType
changeInteractionOrderType
The definition of order type name is located in
RTIA/ObjectManagement.cc
this is currently a "static" list
_
const ObjectManagement::OrderTypeList
ObjectManagement::orderTypeList[] = {
{ "Receive", RECEIVE },
{ "Timestamp", TIMESTAMP },
{ NULL }
};
_
but we may change this if needed.