Project

General

Profile

Actions

Feature #78732

closed

Introduce signals in Application->run

Added by Claus Due over 7 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Could have
Assignee:
-
Category:
System/Bootstrap/Configuration
Target version:
-
Start date:
2016-11-17
Due date:
% Done:

0%

Estimated time:
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

TYPO3 could benefit from two new signals in Application->run method:

public function run(callable $execute = null)
    {
        // Signal one: PreApplication
        $this->bootstrap->handleRequest(\TYPO3\CMS\Core\Http\ServerRequestFactory::fromGlobals());

        if ($execute !== null) {
            call_user_func($execute);
        }

        $this->bootstrap->shutdown();
        // Signal two: PostApplication
    }

The two hooks would be ideal when implementing custom instrumentation with for example NewRelic - the two signals would allow integrating with such instrumentation completely outside TYPO3 request handling.

PS: Other signals considered for __construct on Application as well, to interact with TYPO3 bootstrapping and the Composer autoloader.


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Epic #88027: Properly handle Hooks/Signals and EventsClosedBenni Mack2022-04-22

Actions
Actions #1

Updated by Benni Mack about 5 years ago

  • Related to Epic #88027: Properly handle Hooks/Signals and Events added
Actions #2

Updated by Benni Mack about 4 years ago

  • Status changed from New to Needs Feedback

How would we register a hook if ext_localconf is not loaded before?

Actions #3

Updated by Benni Mack over 2 years ago

  • Status changed from Needs Feedback to Closed

we've removed the callback fully, so the ApplicationLevel should and could be solved by custom applications now

Actions

Also available in: Atom PDF