Needs work
Project:
Collect
Version:
8.x-1.x-dev
Component:
Storage
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
26 Feb 2015 at 13:58 UTC
Updated:
13 Aug 2015 at 12:03 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
corvus_ch commentedI do not see any reason why this should be removed. We now introduced a more structured way of processing with processor plugins. This seems to be the right approach for what we do what to achieve but may not be a match for somebody else. So I suggest that we leave the event based processing inlace just for the reason of options.
So instead of removing it, let's do some clean up. The event based processing now is only triggered by the service and only handled in background. So lets move it to posSave and make it configurable to be executed directly or moved to background processing.
Comment #2
miro_dietikerBecause what you propose is extra work.
We are not saying that this feature is crap. We just say, our current direction does not use it.
And we are trying to limit the codebase and focus work to speedup. Dropping features for this makes sense, because it is fast, reduces complexity.
Usually, we provide a removal patch and commit it. Then keeping the issue open.
Once the need arises again with a real world application, the diffs / patches can be applied in reverse and someone can spend time in completing the feature.
Comment #3
mbovan commentedI'm working on CRM Core Matcher changes (Issue Reimplement Matcher with plugin instances support ) and during CRM Core and Collect integration spotted that this class is no longer used.
Providing a patch to remove left-overs. If we decide to switch to approach
EventSubscriberimplements we can use this patch again to revert the changes.Comment #4
miro_dietikerYou just dropped the EventSubscriber. I committed it for now to drop that complexity.
Note that the whole event processing is still in place:
Comment #5
miro_dietiker