Bug #299
Handle buffer satuaration in spread
| Status: | Resolved | Start date: | 05/17/2011 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: | J. Wienke | % Done: | 100% | |
| Category: | - | |||
| Target version: | 0.3 |
Description
If a client is not fast enough receiving messages, spread at some time kills the connection with error code -8. This must be handled in clients.
Associated revisions
addeda unit test that ensures that SpreadConnection throws an exception on receive if a buffer saturation occurred.
refs #299
generate better exception information in case a receiving error occurs. Nevertheless, this does not pass the information to the client as there is no real ErrorHandler interface right now. This is a separate task...
fixes #299
History
#1 Updated by J. Moringen about 13 years ago
- Target version set to 0.3
#2 Updated by J. Wienke about 13 years ago
- Status changed from New to In Progress
- Assignee set to J. Wienke
#3 Updated by J. Wienke about 13 years ago
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
Applied in changeset r1431.