Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 10/26/2022 in all areas

  1. That's a symptom of session locking. You can work around that by having your long-running process call session_write_close before it starts. Assuming your long delay is an actual problem and any a symptom of poor code, there are a variety of ways to handle moving the task to a background process. Cron is a common and generally easy way to handle it. Another way is to use a job queue / message queue and separate worker services. Examples would be gearman, beanstalkd, rabbitmq, zeromq, and others.
    1 point
This leaderboard is set to New York/GMT-05:00
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.