As a follow up of what was discussed previously in this thread: http://www.orocos.org/forum/rtt/rtt-dev/portbufferfullevent I implemented the suggestion that Peter made: added a boolean field trigger_only_full to ConnPolicy and use that to determine when to fire signal() for a buffered connection. See attached patch. It has not been tested thoroughly, only for my use case, and there it works.
Given the discussion in the mentioned thread, I understand that the patch may not make it into the master. However, it might just be useful for some other users as well, and therefore I thought to submit it anyway.
Cheers, Theo
| Attachment | Size |
|---|---|
| 0001-optionally-signal-when-buffer-full.patch | 5.39 KB |
patch for triggering when buffer of buffered connection is full
On Wednesday 11 May 2011 15:47:06 t [dot] j [dot] a [dot] devries [..] ... wrote:
> As a follow up of what was discussed previously in this thread:
> http://www.orocos.org/forum/rtt/rtt-dev/portbufferfullevent
> I implemented the suggestion that Peter made: added a boolean field
> trigger_only_full to ConnPolicy and use that to determine when to fire
> signal() for a buffered connection. See attached patch. It has not been
> tested thoroughly, only for my use case, and there it works.
>
> Given the discussion in the mentioned thread, I understand that the patch
> may not make it into the master. However, it might just be useful for some
> other users as well, and therefore I thought to submit it anyway.
>
> Cheers, Theo
Thanks Theo. It's not very intrusive so I can't imagine that much objections.
Could you create a bug report and attach the patch inthere ?
Peter