[
https://issues.apache.org/jira/browse/IGNITE-21711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrey Mashenkov updated IGNITE-21711:
--------------------------------------
Description:
ClockWaiter allows to get notification at certain time, but there is no way to
know the current time.
Because of this fact, we have to pass both object (clockWaiter and clock) to
dependant objects.
Let's
1. Add a shortcut for `clock.now()` in ClockWater.
2. Rename ClockWaiter -> ClockService
3. Use ClockService instead of HybridClock in components, which now required
both Clock and ClockWaiter. Or maybe all components, which are not intended to
update clock via `clock.update(timestamp)`
was:
ClockWaiter allows to get notification at certain time, but there is no way to
know the current time.
Because of this fact, we have to pass both object (clockWaiter and clock) to
dependant objects.
Let's
1. Add a shortcut for `clock.now()` in ClockWater.
2. Rename ClockWaiter -> ClockService
3. Use ClockService instead of HybridClock in components, which don't use the
clock directly via `clock.update`
> ClockWaiter refactoring
> -----------------------
>
> Key: IGNITE-21711
> URL: https://issues.apache.org/jira/browse/IGNITE-21711
> Project: Ignite
> Issue Type: Improvement
> Reporter: Andrey Mashenkov
> Priority: Minor
> Labels: ignite-3
>
> ClockWaiter allows to get notification at certain time, but there is no way
> to know the current time.
> Because of this fact, we have to pass both object (clockWaiter and clock) to
> dependant objects.
> Let's
> 1. Add a shortcut for `clock.now()` in ClockWater.
> 2. Rename ClockWaiter -> ClockService
> 3. Use ClockService instead of HybridClock in components, which now required
> both Clock and ClockWaiter. Or maybe all components, which are not intended
> to update clock via `clock.update(timestamp)`
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
