You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have successfully used disruptor-- in one of my projects. However, I would like to support multiple producers in different threads claiming from/publishing to a single ringbuffer. I see that the multi-threaded claim strategy is commented out - I assume because it has not been fully tested? The refactored code in the develop branch looks promising (and includes the multi-threaded claim strategy) - is this ready for use or should I wait until refactoring is fully done?
Thanks,
Fabian
The text was updated successfully, but these errors were encountered:
Your assumptions are both valid. The refactored code is heavily influenced from the varon-t implementation, while the original code is taken almost verbatim from the java implementation.
I have not worked on this project lately, since I haven't had the need to integrate C++ at work.
I see. I am not sure how much I would be able to help out with the refactoring. Given that my code relies on the original disruptor--, I would first like to try to get the multi-threaded claim strategy to work. Are there any known issues that you came across?
Hi,
I have successfully used disruptor-- in one of my projects. However, I would like to support multiple producers in different threads claiming from/publishing to a single ringbuffer. I see that the multi-threaded claim strategy is commented out - I assume because it has not been fully tested? The refactored code in the develop branch looks promising (and includes the multi-threaded claim strategy) - is this ready for use or should I wait until refactoring is fully done?
Thanks,
Fabian
The text was updated successfully, but these errors were encountered: