[
https://issues.apache.org/jira/browse/GEODE-7377?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16963602#comment-16963602
]
John Blum commented on GEODE-7377:
----------------------------------
Turns out, there is already a method in the AsyncEventQueue to ascertain the
paused state of event dispatching...
Since the Javadoc is missing in Apache Geode, sharing the Pivotal GemFire
Javadoc instead...
http://gemfire-98-javadocs.docs.pivotal.io/org/apache/geode/cache/asyncqueue/AsyncEventQueue.html#isDispatchingPaused--
However, this is not very consistent in naming structure. It would have been
better to name the method {{isEventDispatchingEnabled()}}.
{{isDispatchingPaused()}}, while implied, could mean anything.
> AsyncEventQueue should have a isEventDisplatchingPaused() method
> ----------------------------------------------------------------
>
> Key: GEODE-7377
> URL: https://issues.apache.org/jira/browse/GEODE-7377
> Project: Geode
> Issue Type: Improvement
> Components: regions
> Reporter: John Blum
> Priority: Major
>
> This is useful to determine (programmatically) whether the AEQ was created in
> a "paused" state to begin with.
> Anytime you have methods to control the lifecycle (start/stop) of some
> background processing, you should also provide a means to query the state.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
