[concurrency-interest] draft Carrier API

Alex Otenko oleksandr.otenko at gmail.com
Wed Mar 11 07:17:23 EDT 2020

I don't think so.

Count messages sent, and count messages returned by receive. When the count
of receive reaches the number for the message sent using sendSynchronously,
unblock the sendSynchronously.

It is useful as a barrier.


On Wed, 11 Mar 2020, 08:23 Alexei Kaigorodov via Concurrency-interest, <
concurrency-interest at cs.oswego.edu> wrote:

> The method sendSynchronously() requires to wrap each message in an envelope
> which also contains a reference to sender, to pass ack signal. This is a
> pure performance loss for (most frequent) cases where acknowledge is not
> required. Besides, this method has little sense. It notificates sender that
> the message has left the carrier, but did it reached the destination? There
> can be other intermediate steps between the sender and the destination.
> I propose to remove this method.
> --
> Sent from: http://jsr166-concurrency.10961.n7.nabble.com/
> _______________________________________________
> Concurrency-interest mailing list
> Concurrency-interest at cs.oswego.edu
> http://cs.oswego.edu/mailman/listinfo/concurrency-interest
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://cs.oswego.edu/pipermail/concurrency-interest/attachments/20200311/18403f47/attachment.htm>

More information about the Concurrency-interest mailing list