catalyst at mikeraynham
Jun 7, 2011, 1:07 PM
Post #15 of 19
(1215 views)
Permalink
|
On 07/06/11 20:56, David E. Wheeler wrote:
> On Jun 7, 2011, at 12:11 PM, Mike Raynham wrote:
>
>> If QUEUE_PUBLISH_JOBS is turned off and a job's Publish Time is the current time, or in the past, then the job will be executed immediately.
>>
>> If QUEUE_PUBLISH_JOBS is turned off and a job's Publish Time is in the future, then the job will be placed in a queue and checked by the next poll of either bric_queued or bric_dist_mon.
>>
>> If QUEUE_PUBLISH_JOBS is turned on, all jobs will be placed in a queue and processed by the next poll of either bric_queued or bric_dist_mon.
>>
>> It is therefore possible to allow jobs to be published both immediately, and at scheduled times, by turning QUEUE_PUBLISH_JOBS off.
>
> Correct. Not usually recommended, though, as sometimes publish jobs can be quite expensive (triggered publishes), so the UI will appear to hang when a user publishes something *now*. So to keep the UI responsive for users, it's usually best to do queued publishes.
Noted, thanks.
>
>> bric_queued and bric_dist_mon check a job's Publish Time. If the current time is equal to, or greater than, the job's Publish Time, the job will be executed. Otherwise the job will remain in the queue, a re-checked at the next poll.
>>
>> A job's Publish Time does not necessarily coincide with the actual time at which it is published and distributed. If, for example, bric_queued or bric_dist_mon are run as a cron job at 00, 15, 30 and 45 minutes past the hour, a job with a Publish Time of 16:35 will not be executed until 16:45. It is therefore up to the Bricolage administrator to determine the most suitable polling interval for bric_queued or bric_dist_mon.
>>
>> bric_dist_mon fails if ALWAYS_USE_SSL is enabled.
>
> That sounds like a bug.
Yes, I meant to elaborate on that before posting. It returns:
Error sending jobs to distributor.: Unexpected content returned from
http://localhost/dist/:
...and then outputs the HTML from the Bricolage login page. I suspect
that ALWAYS_USE_SSL is causing a redirect that bric_dist_mon is not
expecting.
As bric_queued seems like a better option, I'll just note in the wiki
that bric_dist_mon is no longer the preferred option, and that it
doesn't work with ALWAYS_USE_SSL enabled.
>
>> bric_queued works correctly if ALWAYS_USE_SSL is enabled.
>>
>> ---
>>
>> Finally, are there any good reasons to use bric_dist_mon instead of bric_queued?
>
> Not anymore, no.
>
> Best,
>
> David
>
Regards,
Mike
|
