Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Safe Handler Execution #17

Merged
merged 1 commit into from Mar 14, 2017
Merged

Safe Handler Execution #17

merged 1 commit into from Mar 14, 2017

Conversation

hyperthunk
Copy link
Member

Evaluating safe or apiSafe in a 'filters' block allows the user to mark
certain messages for safe handling. When marked thus, any matching handlers
for these messages are evaluated without fully de-queueing the message from
the priority queue, such that if we receive and handle (i.e. swallow) an
exit signal, the message will be available for re-processing. Only once a
message has been safely processed will it be fully dequeued from the internal
mailbox/queue.

Evaluating 'safe' or 'apiSafe' in a 'filters' block allows the user to mark
certain messages for safe handling. When marked thus, any matching handlers
for these messages are evaluated without fully dequeueing the message from
the priority queue, such that if we receive and handle (i.e. swallow) an
exit signal, the message will be available for re-processing. Only once a
message has been safely processed will it be fully dequeued from the internal
mailbox/queue.
@hyperthunk hyperthunk merged commit 741ae23 into master Mar 14, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant