Enhanced View of Time Avatar
  1. OMG Specification

Enhanced View of Time — All Issues

  • Acronym: EVoT
  • Issues Count: 10
  • Description: All Issues
Open Closed All
All Issues

Issues Descriptions

Section 8.5.4.2

  • Key: EVOT2-4
  • Legacy Issue Number: 11312
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    On 8.5.4.2
    There is a typo error in the formatting

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    To format ยง8.5.4.2 as the other subsection of section 8.5.4

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

LightWeight idl contains some error

  • Key: EVOT2-8
  • Legacy Issue Number: 11316
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    LightWeight idl contains some error (Local vs Local_), some macro (e.g. LW_TIME)
    is not described, some type is not coherent with the complete service (e.g. ClockCatalog),
    consolidate IDL is not present in the spec.

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    To substitute attribute “Local” in module “ClockProperty” with “_Local”.

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

merge CocClockService and LightWeightTime

  • Key: EVOT2-10
  • Legacy Issue Number: 11318
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    Question: does it make sense to merge CocClockService and LightWeightTime in a single file "define" controlled?

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    To include the LightWeight part of the spec in the cosClockService IDL and update the LightWeight part of specification (section 9) accordingly.

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

Forever should be 0x7FF.... instead of 0xFFFF (java problems

  • Key: EVOT2-7
  • Legacy Issue Number: 11315
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    Forever should be 0x7FF.... instead of 0xFFFF (java problems

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    To modify “Forever” attribute value in “0x7FFF”

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

Does it make sense to change the module encapsulation for Monotonicity?

  • Key: EVOT2-9
  • Legacy Issue Number: 11317
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    On 8.8

    Does it make sense to change the module encapsulation for Monotonicity?

    I'd propose

    module Monotonicity
    {
    enum RecoveyStrategy

    { IGNORE, // Ignore violation SLOW_DOWN, // Slow down the clock so to recover monotonicity STALL // Stall the clock up to when the violation condition has been risolved }

    ;

    struct Violation

    { long min_interval; // minimum time interval (in nsec) to be considered as a violation long max_interval; // max time interval (in nsec) to be considered as a violation. Greate interval // will be regarded as clock failure RecoveyStrategy strategy; }

    ;

    local interface ViolationHandler;
    local interface ViolationRegistry

    { // Register an handler for a given clock providing the monotonicity recovering strategy. // By default the monotonicity violation are ignored. void register_handler(in Clock aClock, in Violation aViolation, in ViolationHandler aHandler); void unregister_handler(in ViolationHandler aHandler); }

    ;

    local interface ViolationHandler

    { // void handle_violation(in Clock aClock, in Violation aViolation); }

    ;

    };

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    To introduce a specific module “Monotonicity” to be nested into cosClockService module.

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

fix in the description of parameter

  • Key: EVOT2-6
  • Legacy Issue Number: 11314
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    General
    some fix in the description of parameter (changed names with clash with type e.g. Clock clock -> Clock aClock)

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    To change the names of the attributes as, for example: Clock clock -> Clock aClock

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

ClockCatalog mismatch

  • Key: EVOT2-3
  • Legacy Issue Number: 11311
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    ClockCatalog is an uncostrained interface in the spec description but not in the idl, I propose to maintain it uncostrained everywhere.

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    To maintain ClockCatalog interface unconstrained in the EVoT services (lightweight or not).

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

Section 8.8

  • Key: EVOT2-5
  • Legacy Issue Number: 11313
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    On 8.8
    Monotonicity handling is not in the IDL

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    See issue 11317 for disposition

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

Section 8.4.2 - typo

  • Key: EVOT2-2
  • Legacy Issue Number: 11310
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    On 8.4.2
    typo error getRaises instead of raises

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    See issue 11309 for disposition

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

Section 8.4.2

  • Key: EVOT2-1
  • Legacy Issue Number: 11309
  • Status: closed  
  • Source: Selex ES ( Fabrizio Morciano)
  • Summary:

    On 8.4.2
    current_time is a readonly attribute: this way to declare a method
    doesn't offer a great added value instead of a simple current_time method,
    my proposal is to change it in a method
    TimeBase::TimeT current_time()
    this also improve the idl compilation capabilities, indeed some idl compiler
    (e.g. JacORB and omniORB) fails with readonly attribute and raises keywords.

  • Reported: EVoT 2.0b1 — Wed, 29 Aug 2007 04:00 GMT
  • Disposition: Resolved — EVoT 2.0
  • Disposition Summary:

    To substitute the readonly attribute “current_time” in Clock interface with “TimeBase::TimeT current_time()” method.

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