Project

General

Profile

Feature #20115

Support extended clock event specification

Added by Richard Neswold over 1 year ago.

Status:
New
Priority:
Normal
Category:
Data Pool Manager
Target version:
Start date:
06/07/2018
Due date:
% Done:

0%

Estimated time:
Duration:

Description

Need to support the new, extended clock event specification. Since it will take a while for front-ends to upgrade to the latest MOOC, we need be careful to maintain compatibility.

Clock events that don't have a clock type field can be passed on to the front-end. Old front-ends support this format and new front-ends recognize this form to mean "use whatever clock you have."

When a clock type is specified, and to maintain strict backward-compatibility, DPM may need to maintain a table of (front-end -> clock type) mappings so it would know whether a request can be sent to a front-end (in fact, this mapping may remove the need to update front-ends at all!) Discussion is encouraged.


Related issues

Related to Data Request Format - Feature #22092: Multiple Clock Events for RequestsNew03/07/2019

Blocked by TCLK Infrastructure - Feature #20113: Support the extended clock specificationAssigned06/07/2018

History

#1 Updated by Richard Neswold over 1 year ago

  • Blocked by Feature #20113: Support the extended clock specification added

#2 Updated by Richard Neswold 6 months ago



Also available in: Atom PDF