Skip to main content
2 of 3
deleted 107 characters in body

Best Practices for Implementing a Heartbeat Feature in a Laravel App to Track Offline Status

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.