On Fri, May 27, 2011 at 8:10 PM, Julian Edwards
<email address hidden> wrote:
> On Friday 27 May 2011 04:40:44 you wrote:
>> Ah, I think there is a layering confusion here.
>>
>> At the package layer we certainly need to know that there is something
>> waiting for an archive admin to approve.
>>
>> At the queue layer we don't want stuff in a queue that can't be
>> processed: they shouldn't be queued for handling by the job runner.
>
> Why not?
Its incompatible design wise with zeromq/rabbitmq etc. Stuff in a
queue needs to be actionable.
On Fri, May 27, 2011 at 8:10 PM, Julian Edwards
<email address hidden> wrote:
> On Friday 27 May 2011 04:40:44 you wrote:
>> Ah, I think there is a layering confusion here.
>>
>> At the package layer we certainly need to know that there is something
>> waiting for an archive admin to approve.
>>
>> At the queue layer we don't want stuff in a queue that can't be
>> processed: they shouldn't be queued for handling by the job runner.
>
> Why not?
Its incompatible design wise with zeromq/rabbitmq etc. Stuff in a
queue needs to be actionable.
-Rob