Enhancement #1083
Implement communication with congestion control (for reader interface)
| Status: | In Progress | Start date: | 07/17/2012 | ||
|---|---|---|---|---|---|
| Priority: | Normal | Due date: | |||
| Assignee: | - | % Done: | 10% | ||
| Category: | Protocol | ||||
| Target version: | rsb-1.0 |
Description
I have a client program using the reader interface for the socket transport in C++, which provides the bus server for a bag-play. After receiving some events the client program receives a SIGKILL and terminates. This occurs because the client is too slow and the socket InPullConnector internally has a queue which then fills up.
Generally, for a reader interface to be useful, some kind of synchronized processing in pipelines with congestion control would be useful.
History
#1 Updated by J. Wienke almost 12 years ago
Maybe there is no congestion control with the socket transport?
#2 Updated by J. Wienke almost 12 years ago
- Tracker changed from Bug to Enhancement
- Subject changed from socket bus-server program receiving over the reader interface gets killed to Implement communication with congestion control (for reader interface)
- Description updated (diff)
- Category changed from C++ to Protocol
- Assignee deleted (
J. Moringen) - Target version deleted (
rsb-0.7)
#3 Updated by J. Moringen about 11 years ago
- Target version set to rsb-0.10
I think, this should be tackled as part of our more general flow control plans. Just delaying for now, though.
#4 Updated by J. Moringen over 10 years ago
- Status changed from New to In Progress
- % Done changed from 0 to 10
A prototypical implementation can be found in the wip-flow-control branch of the rsb-cl repository.
#5 Updated by J. Moringen over 10 years ago
- Target version changed from rsb-0.10 to rsb-0.11
#6 Updated by J. Moringen over 10 years ago
- Target version changed from rsb-0.11 to rsb-0.12
#7 Updated by J. Moringen about 9 years ago
- Target version changed from rsb-0.12 to rsb-1.0