About an hour ago I left a comment here, which is now gone. I admit it was somewhat lengthy, but it was directly referring to the topics of this talk. Is there any policy, about which comments are left in? My comment in short was the following: - I think there is a race condition in the get() function of the monitor example. - The static_cast in the monitor example is not directly connected to CRTP in particular, but to more general lazy template instantiation. - It would have been nice, to also refer to more modern implementations of these patterns (Executors etc)
Let me add one important ActiveObject disadvantage: performance. And I don't mean the serialization/scheduler overhead. I mean the fact that for the whole duration of the handling of a command, no other command can be executed. This can easily lead to bottleneck, when - if fact - data that needs to be protected from data races, can be kept locked for a relatively short period of time. One might say that this is yet another disadvantage of object-oriented programming. If you couple data with logic, then you can NOT simply: lock data, fetch value, unlock data, operate on value. You have to greatly prolong the lock duration.
Thank CPPCON and Mr.Grimm for keep educating us
About an hour ago I left a comment here, which is now gone. I admit it was somewhat lengthy, but it was directly referring to the topics of this talk.
Is there any policy, about which comments are left in?
My comment in short was the following:
- I think there is a race condition in the get() function of the monitor example.
- The static_cast in the monitor example is not directly connected to CRTP in particular, but to more general lazy template instantiation.
- It would have been nice, to also refer to more modern implementations of these patterns (Executors etc)
Thank you for this indepth talk about a very complex topic.
auto generated subtitles are in german (so unusable). Is it possible for the author of the video to force subtitle language to english ? thanks
Let me add one important ActiveObject disadvantage: performance. And I don't mean the serialization/scheduler overhead. I mean the fact that for the whole duration of the handling of a command, no other command can be executed. This can easily lead to bottleneck, when - if fact - data that needs to be protected from data races, can be kept locked for a relatively short period of time. One might say that this is yet another disadvantage of object-oriented programming. If you couple data with logic, then you can NOT simply: lock data, fetch value, unlock data, operate on value. You have to greatly prolong the lock duration.
Yes but there is nothing that prevents the active object to use multiple threads to pick multiple items from the activation list
Active objects are good patterns for a subsystem boundary abstraction
Thanks!