Hi Zdravko,
On Wed, Feb 29, 2012 at 4:09 AM, Zdravko Balorda
<zdravko.balorda@siix.com>wrote:
> And, Bulk publish via UI should also schedule jobs under lowest priority.
>>>
>> Why lowest priority?
>>
>
> I consider Bulk Publish to be another way of massive publishing. If forced
> to low priority
> it won't interfere with other people working.
>
This concept was posted in the following feature request:
http://bricolage.lighthouseapp.com/projects/29601/tickets/191. Per the
ticket, I would prefer that Bulk Publish allow the user to select a
priority.
It is a parameter to a $burner->publish, but not to publish_another().
> Maybe it's even
> beter, because of proper handling the default priority. For
> publish_another() it's probably the best to always go with calling job
> priority. If not defined otherwise
> it will be the same as the publishing story priority, anyway.
>
You might take a look at some of the commits on my Bricolage fork in GitHub
(see the "Denison" branch) during April 2011:
https://github.com/nlegg/bricolage/commits/denison for some tips here.
David helped us out with a number of publish priority-related patches, and
I implemented a quick fix so publish_another() calls wouldn't use Bric's
internal queue (discussed here:
http://www.gossamer-threads.com/lists/bricolage/users/39682).
Good luck,
Nick
On Wed, Feb 29, 2012 at 4:09 AM, Zdravko Balorda
<zdravko.balorda@siix.com>wrote:
> And, Bulk publish via UI should also schedule jobs under lowest priority.
>>>
>> Why lowest priority?
>>
>
> I consider Bulk Publish to be another way of massive publishing. If forced
> to low priority
> it won't interfere with other people working.
>
This concept was posted in the following feature request:
http://bricolage.lighthouseapp.com/projects/29601/tickets/191. Per the
ticket, I would prefer that Bulk Publish allow the user to select a
priority.
It is a parameter to a $burner->publish, but not to publish_another().
> Maybe it's even
> beter, because of proper handling the default priority. For
> publish_another() it's probably the best to always go with calling job
> priority. If not defined otherwise
> it will be the same as the publishing story priority, anyway.
>
You might take a look at some of the commits on my Bricolage fork in GitHub
(see the "Denison" branch) during April 2011:
https://github.com/nlegg/bricolage/commits/denison for some tips here.
David helped us out with a number of publish priority-related patches, and
I implemented a quick fix so publish_another() calls wouldn't use Bric's
internal queue (discussed here:
http://www.gossamer-threads.com/lists/bricolage/users/39682).
Good luck,
Nick