Package google.registry.batch

Class AsyncTaskEnqueuer

java.lang.Object

google.registry.batch.AsyncTaskEnqueuer

public final class AsyncTaskEnqueuer
extends Object

Helper class to enqueue tasks for handling asynchronous operations in flows.

Field Summary

Fields

Modifier and Type	Field	Description
static final String	PARAM_REQUESTED_TIME
static final String	PARAM_RESAVE_TIMES
static final String	PARAM_RESOURCE_KEY	The HTTP parameter names used by async flows.
static final String	QUEUE_ASYNC_ACTIONS	The task queue names used by async flows.

Constructor Summary

Constructors

Constructor	Description
AsyncTaskEnqueuer(CloudTasksUtils cloudTasksUtils)

Method Summary

Modifier and Type	Method	Description
void	enqueueAsyncResave(VKey<? extends EppResource> entityKey, org.joda.time.DateTime now, com.google.common.collect.ImmutableSortedSet<org.joda.time.DateTime> whenToResave)	Enqueues a task to asynchronously re-save an entity at some point(s) in the future.

Methods inherited from class java.lang.Object

clone, equals, finalize, getClass, hashCode, notify, notifyAll, toString, wait, wait, wait

Field Details

PARAM_RESOURCE_KEY

public static final String PARAM_RESOURCE_KEY

The HTTP parameter names used by async flows.

See Also:

• Constant Field Values

PARAM_REQUESTED_TIME

public static final String PARAM_REQUESTED_TIME

See Also:

• Constant Field Values

PARAM_RESAVE_TIMES

public static final String PARAM_RESAVE_TIMES

See Also:

• Constant Field Values

QUEUE_ASYNC_ACTIONS

public static final String QUEUE_ASYNC_ACTIONS

The task queue names used by async flows.

See Also:

• Constant Field Values

Constructor Details

AsyncTaskEnqueuer

@Inject
public AsyncTaskEnqueuer(CloudTasksUtils cloudTasksUtils)

Method Details

enqueueAsyncResave

public void enqueueAsyncResave(VKey<? extends EppResource> entityKey,
 org.joda.time.DateTime now,
 com.google.common.collect.ImmutableSortedSet<org.joda.time.DateTime> whenToResave)

Enqueues a task to asynchronously re-save an entity at some point(s) in the future.

Multiple re-save times are chained one after the other, i.e. any given run will re-enqueue itself to run at the next time if there are remaining re-saves scheduled.