[jboss-jira] [JBoss JIRA] (JGRP-2172) Non-blocking flow control

[Bela Ban (JIRA)]

     [ https://issues.jboss.org/browse/JGRP-2172?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bela Ban updated JGRP-2172:
---------------------------
    Description: 
Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.

Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded)

The queued messages are sent when credits arrive. 

Non-blocking flow control can be used by both external and internal threads.

If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.


  was:
Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.

Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded)

The queued messages are sent when credits arrive. 

Non-blocking flow control can be used by both external and internal threads.




> Non-blocking flow control
> -------------------------
>
>                 Key: JGRP-2172
>                 URL: https://issues.jboss.org/browse/JGRP-2172
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Bela Ban
>             Fix For: 4.0.4
>
>
> Sending a message through FlowControl (UFC, MFC) should not block if {{Message.Flag.NB_FC}} (non-blocking flow control) is set.
> Instead, the message should be added to a queue (bounded if {{max_size}} > 0, else unbounded)
> The queued messages are sent when credits arrive. 
> Non-blocking flow control can be used by both external and internal threads.
> If the queue is unbounded, then it is the responsibility of the application (e.g. Infinispan) to make sure the queue doesn't grow to an untenable size.



--
This message was sent by Atlassian JIRA
(v7.2.3#72005)