Shulou(Shulou.com)05/31 Report--

This article mainly introduces the relevant knowledge of Laravel event monitoring method case analysis, the content is detailed and easy to understand, the operation is simple and fast, and has a certain reference value. I believe you will gain something after reading this Laravel event monitoring method case analysis article. Let's take a look.

Laravel Event & Listener event monitoring mechanism allows developers not only to organize the code in a more organized way, but also a highly abstract mapping of the operating rules of the real society, which is also the case in our real society. We monitor the changes of things and respond to them, so that things develop as we expect. When reality is mapped into code logic, events and their handling logic are usually separated. After all, not all events need to be processed immediately. Combined with the queue, we can make the workflow of event monitoring and processing more perfect.

Use case:

Listen for log log file size change

User login: record the number of user logins and access-related information

Implement event listening steps:

1. Create event: event

2. Create a monitor: listener

3. Bind events and monitor

4. Trigger event

First, manually create events and monitor

1. Create a login event: event

App/Events/UserLogin.php

Php artisan make:event UserLogin// gets user information instance public function _ _ construct (User $user) {$this- > user = $user;}

2. Create user login email to send monitoring, and bind UserLogin login event: listener

App/Listeners/EmailAdminUserLogin.php

Php artisan make:listener EmailAdminUserLogin-event=UserLogin / / log print login user information public function handle (UserLogin $event) {/ / dd ($event); / / log print login user information Log::info ($event- > user- > name. 'logged in');}

3. The binding relationship between registration events and monitoring

An event can correspond to multiple listeners

App/Providers/EventServiceProvider.php

Protected $listen = ['App\ Events\ UserLogin' = > [' App\ Listeners\ EmailAdminUserLogin',],]

4. Trigger the event when the user logs in

App/Http/Controllers/Auth/LoginController.php

/ / override the authenticated method protected function authenticated of AuthenticatesUsers class (Request $request, $user) {/ / trigger event event (new UserLogin ($user));} II. Quickly generate events and monitor

Here, the corresponding events and listeners are generated according to the attribute listen in app/Providers/EventServiceProvider.php.

This is the end of php artisan event:generate 's article on "case analysis of Laravel event monitoring methods". Thank you for reading! I believe you all have a certain understanding of the knowledge of "case analysis of Laravel event monitoring methods". If you want to learn more, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.