Timeline for Best Practices for Implementing a Heartbeat Feature in a Laravel App to Track Offline Status
Current License: CC BY-SA 4.0
11 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Aug 10 at 16:46 | answer | added | guest271314 | timeline score: -1 | |
| Jul 15 at 20:00 | history | edited | Doc Brown | CC BY-SA 4.0 | added 7 characters in body |
| Jul 15 at 9:24 | history | protected | gnat | ||
| Jul 14 at 17:13 | answer | added | Arseni Mourzenko | timeline score: 5 | |
| Jul 14 at 17:06 | history | edited | meowyn0316 | CC BY-SA 4.0 | deleted 107 characters in body |
| Jul 14 at 11:15 | answer | added | Basilevs | timeline score: 4 | |
| Jul 14 at 9:08 | review | Close votes | |||
| Jul 20 at 3:06 | |||||
| Jul 14 at 7:08 | comment | added | meowyn0316 | What I meant is that the client will send a heartbeat signal to the server every X seconds. The server listens for this signal, and if it doesn't receive a response within the set interval, it marks the app as "offline." Once the signal is re-established, the server updates the app’s status to "online." | |
| Jul 14 at 6:58 | comment | added | Philip Kendall | What exactly do you mean by an "offline message"? You clearly can't send a message from the client app if the client app is offline, that's the definition of "offline". | |
| S Jul 14 at 6:48 | review | First questions | |||
| Jul 14 at 17:22 | |||||
| S Jul 14 at 6:48 | history | asked | meowyn0316 | CC BY-SA 4.0 |