Home/ Questions/Q 8119001
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T04:40:14+00:00

I have made a simple chat application in PHP/Ajax/MySQL. I am regularly calling these

  • 0

I have made a simple chat application in PHP/Ajax/MySQL.

I am regularly calling these two methods-

setInterval("GetChatParticipants()",5000);
setInterval("GetChatMessages()",1000);

Now as per client design, there’s no Logout or Sign Out button, so I want to detect when user closes the browser and at that time I have to delete the participant record from the database. I dont want to use onbeforeunload as Chrome refuses to accept Ajax requests on window unload event.

So I am thinking of implementing in Ajax by making repeated reqests. But the question is how exactly shall I do that. Shall I update the Participant table with last_active_time and if the difference between current time and that last_active_time is , say, more than 10 min, then I should delete the user? Is it a practical solution or could there be a better one?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    You have the best solution IMO. In Javascript create a “ping” function that pings every minute / two minutes etc with a session ID unique to that browser/session. Have a sessions table on your server and update when you get a ping. Have another script that looks for entries that have not been pinged for long periods and close the sessions.

    I’ve had this structure running for thousands of concurrent users on one site, and I had to drop the ping down from 1 minute to every 2 minutes when load got heavyish (that was on 2 load balanced servers while running the rest of the site too). Obviously you make your ping approx 45% of the time-out time (so if one fails, a second should hit). It’s a simple process that can handle the load.

    Edit: don’t use “setInterval” for the ping, but user “setTimeout” when each ping either returns or fails. Otherwise, with setInterval, if your server gets too loaded then the pings queue, never respond and queue some more. You get a meltdown of the server as all server sockets are used, then you can’t connect by ssh to fix it… not a moment I was proud of.

    • 0