I'm trying to implement a heartbeat feature for offline tracking that just sends an offline message to the server once the web browser app (Laravel-based) is offline. Ideally it will ping the app's URL every x seconds and then push an offline message to the remote MySQL database if the response fails.

Q's I have in mind are:

1. Should I use the pinging logic from client-side or there's a way to do it server-side.

I'm trying to implement a heartbeat feature for offline tracking that just sends an offline message to the server once the web browser app (Laravel-based) is offline. Ideally it will ping the app's URL every x seconds and then push an offline message to the remote MySQL database if the response fails.

The question I have in mind is:

• Should I use the pinging logic from client-side or there's a way to do it server-side.

I'm trying to implement a heartbeat feature for offline tracking that just sends an offline message to the server once the web browser app (Laravel-based) is offline. Ideally it will ping the app's URL every x seconds and then push an offline message to the remote MySQL database if the response fails.

Q's I have in mind are:

1. Should I use the pinging logic from client-side or there's a way to do it server-side.
2. Are there any Laravel libraries or packages that I can use that will be useful for the heartbeat system?

I'm trying to implement a heartbeat feature for offline tracking that just sends an offline message to the server once the web browser app (Laravel-based) is offline. Ideally it will ping the app's URL every x seconds and then push an offline message to the remote MySQL database if the response fails.

Q's I have in mind are:

1. Should I use the pinging logic from client-side or there's a way to do it server-side.