These are chat archives for atomix/atomix

10th
Dec 2016
belowm
@belowm
Dec 10 2016 03:49
I don't think
belowm
@belowm
Dec 10 2016 03:56
I don't think this would be a good solution, since this would consume a lot of cpu power (busy loop). The java.util.concurrent.BlockingQueue uses object.wait / object.notify to park the thread.
belowm
@belowm
Dec 10 2016 04:02
@neverfox If this is not feasible for some reason, maybe you can consider making the collections observable, so that listeners can be attached that get notified whenever a change happens to a collection. This would possibly be useful for other scenarios as well.
Roman Pearah
@neverfox
Dec 10 2016 22:25
@belowm Ah, you're right about the implementation. I was working off memory. @kuujo Is there a reason that DistributedQueue cannot implement java.util.concurrent.BlockingQueue?