zdravko.balorda at siix
Mar 1, 2012, 1:22 AM
Post #28 of 31
David E. Wheeler wrote:
>> And one more thing about publish another: a new job should be created also if an existing
>> job has different priority than the calling job. It probably comes from another queue or
>> from UI publish.
> That makes sense. You also want to look at the publish time carefully, and make sure it's
> for the same version of the story/media document. If it's too far in the future, you don't
> want to update it.
Actually it gets simpler. There is no need for pushing the scheduled time. If a job
exitsts, and it comes from the past, and it has the same priority then there is nothing
to do more.
If not, create a new job for a given business asset. That's all. Bric_queued will handle
the job properly, publishing it at the end.
>> Occasionally I get an error: Cannot change scheduled time on executing job.
>> This seems to be the price for parallel publishing. It should be extremely rare, though.
> Yeah, that ought to be avoidable, or at least possible to catch and ignore.
And, there are no more such errors. A single database lookup covers for another_queue.
I'm not sure if this also solves the circular publishing problem, though.
Best regards, Zdravko