-
Notifications
You must be signed in to change notification settings - Fork 36
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
Move delivery to dedicated delivery thread #8
Comments
2006-08-24 17:45:08: jwulp@win.tue.nl changed status from new to assigned |
2006-08-31 17:11:46: jwulp@win.tue.nl changed priority from minor to major |
2006-08-31 17:11:46: jwulp@win.tue.nl changed type from enhancement to task |
2006-09-03 19:41:59: jwulp@win.tue.nl changed status from assigned to closed |
2006-09-03 19:41:59: jwulp@win.tue.nl changed resolution from ** to fixed |
2006-09-03 19:41:59: jwulp@win.tue.nl commentedFixed in revision 1867 |
This was referenced May 25, 2018
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue migrated from trac ticket # 8
component: squadt | priority: major | resolution: fixed
2006-08-24 17:44:59: jwulp@win.tue.nl created the issue
With the delivery of every incoming message a thread is created to do the delivery in the background. The drawback of this approach is that if messages arrive fast enough multiple threads may exist concurrently for delivery to the same task (this gives a higher overhead than necessary).
The text was updated successfully, but these errors were encountered: