Follow up for #1599622-8: Run poormanscron via a non-blocking HTTP request
Problem/Motivation
The whole function should probably be moved into a separate listener (it is only invoked by RequestCloseSubscriber) that gets all the things injected. That is, however, not trivial as "the things" means CacheFactory, KeyValueFactory for state, Lock*, guzzle client and there's the do-not-execute-this-on-ajax-requests @todo in RequestCloseSubscriber.
Proposed resolution
Move lock/Guzzle function to separate listener
Remaining tasks
- clarify/correct issue summary
- ...
User interface changes
No UI changes anticipated.
API changes
Yes, moving the function (?)
Comments
Comment #1
yesct commentedNeeds clarification on what function is to be moved.
Any other detailed next steps would be awesome.
Comment #2
berdirComment #16
longwaveThis was done in #2220687: Convert system_run_automated_cron into a subscriber for KernelEvents::TERMINATE