Re: continue working after finishing up with the http client
| From: | Tom Worster | Date: | Wed, 27 May 2009 18:28:12 +0000 |
| Subject: | Re: continue working after finishing up with the http client | ||
| References: | 1 | Groups: | php.general |
| Request: | Send a blank email to php-general+get-293236@lists.php.net to get a copy of this message | ||
On 5/27/09 10:33 AM, "David Otton" <phpmail@jawbone.freeserve.co.uk> wrote:
> 2009/5/27 Tom Worster <fsb@thefsb.org>:
>
>> without getting into whether or not this cache design makes sense, my
>> question in this example is: what options are there for ending the http
>> transition and then continuing on to do the cache update work?
>
> You either continue processing then-and-there (exec(), or whatever) or
> you put the job in queue to be dealt with at your leisure.
>
> The queue is the better solution if you're concerned about processor
> load, as you can prioritise it. The exec() is simpler to implement.
in the absence of a tidy way to close the http connection to the client in
mid-php script, i think the queue will be my better bet. if i use mysql to
implement the queue then i'll have some convenient options for handling it.