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

Explore collision scenario where messages received cause previously transmitted message to timeout #49

Closed
GoogleCodeExporter opened this issue Mar 14, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

It appears that every time an asynchronous message is received when a previous 
message was transmitted, the transmitted message never gets a response. It 
seems the asynchronous received message collides or blocks the previously 
transmitted message's response.

We should explore code that shortens this scenario when the asynchronous 
message is received if a previous outstanding message exists, terminating the 
wait for a response and just retransmit the previous message again.

Original issue reported on code.google.com by idahovoi...@gmail.com on 21 Oct 2011 at 4:50

@GoogleCodeExporter
Copy link
Author

I'm pretty sure this has long since been addressed.  There were a number of 
changes made to properly track such things several months ago.  

Original comment by pnau...@gmail.com on 14 Aug 2012 at 3:06

  • Changed state: Fixed

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

No branches or pull requests

1 participant