-
Notifications
You must be signed in to change notification settings - Fork 0
feat(broker): featured broker events logic #24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Voronapxl
commented
Dec 19, 2025
- Featured logic for events when scenarios are updated with objects or zones, F22 cache will be terminated for such events
1. Continuation of broker logic features
1.Featured logic for events when scenarios are updated with objects or zones, F22 cache will be terminated for such events
1. Deletion of redundant broker logic for cache invalidation 2. Featured extermination of consumer and producer workers
1. invalidation methods putted to thread
| async def handle(self, event: EventT, ctx: Message = None): | ||
| return await self._core.process(event) | ||
|
|
||
| return await self._handle_cache_invalidation(event, ctx) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Мне казалось, суть Mixin'а в том, чтобы придать классу поведение (то есть сразу в нем создать метод handle, а в наследниках вообще ничего не трогать; менее прозрачно, но если вызывать методы самостоятельно, то можно было и просто инкапсуляцией ограничиться.
Не критично, но странновато
1. KafkaProducerClient init_loop set to False
1. KafkaProducerClient init_loop at start