-
Notifications
You must be signed in to change notification settings - Fork 45
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
Correctly handle the messages from time-out requests #109
Labels
Comments
kennethlakin
added a commit
to kennethlakin/shotgun
that referenced
this issue
Nov 9, 2015
This addresses Issue inaka#109, and then some. When a request is made, shotgun:request makes a fresh reference and passes that along with the work to the shotgun FSM. When a request times out, shotgun:request now sends an async request to cancel the now-useless unit of work, passing along the reference for identification, before notifying the client of the request timeout. Things to know: * Gun has its own request queue. So, if a request has made it to gun, cancellation of the request will only squelch future messages that would have come from that request. It is -however- safe to bounce back to at_rest (as we now do), as messages from the cancelled request will not be sent back to the FSM. * Removal of queued requests makes use of queue:filter. For large queues, this is kinda not fast. Minor changes: * state typedef moved up with the other typedefs. * enqueue_work_or_stop slightly simplified.
kennethlakin
added a commit
to kennethlakin/shotgun
that referenced
this issue
Nov 9, 2015
This addresses Issue inaka#109, and then some. When a request is made, shotgun:request makes a fresh reference and passes that along with the work to the shotgun FSM. When a request times out, shotgun:request now sends an async request to cancel the now-useless unit of work, passing along the reference for identification, before notifying the client of the request timeout. Things to know: * Gun has its own request queue. So, if a request has made it to gun, cancellation of the request will only squelch future messages that would have come from that request. It is -however- safe to bounce back to at_rest (as we now do), as messages from the cancelled request will not be sent back to the FSM. * Removal of queued requests makes use of queue:filter. For large queues, this is kinda not fast. Minor changes: * state typedef moved up with the other typedefs. * enqueue_work_or_stop slightly simplified.
kennethlakin
added a commit
to kennethlakin/shotgun
that referenced
this issue
Nov 9, 2015
This addresses Issue inaka#109, and then some. When a request is made, shotgun:request makes a fresh reference and passes that along with the work to the shotgun FSM. When a request times out, shotgun:request now sends an async request to cancel the now-useless unit of work, passing along the reference for identification, before notifying the client of the request timeout. Things to know: * Gun has its own request queue. So, if a request has made it to gun, cancellation of the request will only squelch future messages that would have come from that request. It is -however- safe to bounce back to at_rest (as we now do), as messages from the cancelled request will not be sent back to the FSM. * Removal of queued requests makes use of queue:filter. For large queues, this is kinda not fast. Minor changes: * state typedef moved up with the other typedefs. * enqueue_work_or_stop slightly simplified.
kennethlakin
added a commit
to kennethlakin/shotgun
that referenced
this issue
Nov 10, 2015
This addresses Issue inaka#109, and then some. When a request is made, shotgun:request makes a fresh reference and passes that along with the work to the shotgun FSM. When a request times out, shotgun:request now sends an async request to cancel the now-useless unit of work, passing along the reference for identification, before notifying the client of the request timeout. Things to know: * Gun has its own request queue. So, if a request has made it to gun, cancellation of the request will only squelch future messages that would have come from that request. It is -however- safe to bounce back to at_rest (as we now do), as messages from the cancelled request will not be sent back to the FSM. * Removal of queued requests makes use of queue:filter. For large queues, this is kinda not fast. Minor changes: * state typedef moved up with the other typedefs. * enqueue_work_or_stop slightly simplified.
kennethlakin
added a commit
to kennethlakin/shotgun
that referenced
this issue
Nov 11, 2015
This addresses Issue inaka#109, and then some. When a request is made, shotgun:request makes a fresh reference and passes that along with the work to the shotgun FSM. When a request times out, shotgun:request now sends an async request to cancel the now-useless unit of work, passing along the reference for identification, before notifying the client of the request timeout. Things to know: * Gun has its own request queue. So, if a request has made it to gun, cancellation of the request will only squelch future messages that would have come from that request. It is -however- safe to bounce back to at_rest (as we now do), as messages from the cancelled request will not be sent back to the FSM. * Removal of queued requests makes use of queue:filter. For large queues, this is kinda not fast. Minor changes: * state typedef moved up with the other typedefs. * enqueue_work_or_stop slightly simplified.
kennethlakin
added a commit
to kennethlakin/shotgun
that referenced
this issue
Nov 11, 2015
This addresses Issue inaka#109, and then some. When a request is made, shotgun:request makes a fresh reference and passes that along with the work to the shotgun FSM. When a request times out, shotgun:request now sends an async request to cancel the now-useless unit of work, passing along the reference for identification, before notifying the client of the request timeout. Things to know: * Gun has its own request queue. So, if a request has made it to gun, cancellation of the request will only squelch future messages that would have come from that request. It is -however- safe to bounce back to at_rest (as we now do), as messages from the cancelled request will not be sent back to the FSM. * Removal of queued requests makes use of queue:filter. For large queues, this is kinda not fast. Minor changes: * state typedef moved up with the other typedefs. * enqueue_work_or_stop slightly simplified.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
For more information please check here.
The text was updated successfully, but these errors were encountered: