${taskforce.name} Avatar
  1. OMG Task Force

Clock Service And Executor FTF — Open Issues

  • Key: TIME
  • Issues Count: 3
Open Closed All
Issues not resolved

Issues Descriptions

Elapsed Time since 10/15/1582

  • Key: TIME-6
  • Legacy Issue Number: 1985
  • Status: open  
  • Source: Anonymous
  • Summary:

    Summary: Questions: Is there a formula to determine the amount of elapsed time
    >since 10/15/1582 as specified in the TimeService Specification?
    >
    >After finding that September of 1752 only has 19 days and
    >a few different interpretations of leap year rules, I believe
    >there is some ambiguity as to what should be placed in a
    >TimeBase::Utc time value to represent a specific date/time.
    >

  • Reported: TIME 1.0b1 — Tue, 22 Sep 1998 04:00 GMT
  • Updated: Wed, 11 Mar 2015 04:50 GMT

Obsolete reference to readout operation?

  • Key: TIME-2
  • Legacy Issue Number: 5625
  • Status: open  
  • Source: Floorboard Software ( Jonathan Biggar)
  • Summary:

    Section 2.8.1.2 of the Enhanced Time specification mentions the readout
    operation. Should that be a Clock::current_time attribute instead?

  • Reported: TIME 1.0 — Sun, 1 Sep 2002 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT

Clock Interface

  • Key: TIME-1
  • Legacy Issue Number: 4587
  • Status: open  
  • Source: comcast.net ( Dock Allen)
  • Summary:

    The enhanced views of time added an interface for user-defined clocks,
    including requesting synchronized time. However, there is no way to
    tell the ORB what clock to use for the build in CORBA time-related
    functions (timeouts, etc). At a minimum, it would be good to be able to
    get a synchronized ORB clock. Can we move these interfaces into CORE
    for RT CORBA?

  • Reported: TIME 1.0 — Wed, 3 Oct 2001 04:00 GMT
  • Updated: Fri, 6 Mar 2015 20:58 GMT