[cups] Completed jobs returned older first in 2.0?

[Michael Sweet]

Alex,

This is expected; the web UI does its own sorting.


> On Sep 1, 2015, at 9:32 AM, Alex Korobkin <korobkin+cups at gmail.com> wrote:
> 
> Thanks Michael. Let's look into completed jobs only. RFC2911 says that
> completed jobs should be returned newest first. I see completed jobs in the
> Web UI being returned as oldest first. Is it expected or a bug?
> 
> On Tue, Sep 1, 2015 at 8:29 AM, Michael Sweet <msweet at apple.com> wrote:
> 
>> Alex,
>> 
>> RFC 2911 only defines the order of 'completed' and 'not-completed'.  The
>> other "which-jobs" values are defined in PWG 5100.11 without an ordering
>> requirement.
>> 
>> 
>>> On Aug 31, 2015, at 3:24 PM, Alex Korobkin <korobkin+cups at gmail.com>
>> wrote:
>>> 
>>> Do you mean https://www.cups.org/str.php?L4396 ?
>>> 
>>> It says this:
>>> 
>>>     - If the client requests all 'completed' Jobs (Jobs in the
>>>       'completed', 'aborted', or 'canceled' states), then the Jobs are
>>>       returned newest to oldest (with respect to actual completion
>>>       time)
>>> 
>>> However, I see oldest to newest when i click "See completed jobs" and
>>> newest to oldest when i click "See all jobs".
>>> 
>>> it is slightly confusing and I don't understand why the behavior should
>>> differ. RFC doesn't seem to state that.
>>> 
>>> On Mon, Aug 31, 2015 at 2:23 PM, Michael Sweet <msweet at apple.com> wrote:
>>> 
>>>> CUPS 2.0 fixed a long-standing bug with the order of jobs that were
>>>> returned so that we are now compliant with RFC 2911's requirements.  You
>>>> can click in the job ID field to reverse the order.
>>>> 
>>>> 
>>>>> On Aug 31, 2015, at 12:49 PM, Alex Korobkin <korobkin+cups at gmail.com>
>>>> wrote:
>>>>> 
>>>>> Hi all,
>>>>> 
>>>>> I'm testing CUPS 2.0.4 and noticed that completed jobs in Web UI are
>>>>> returned in the ascending order -- older jobs first. This is different
>>>> from
>>>>> the CUPS 1.7 and earlier versions.
>>>>> 
>>>>> Is it just me (I have multiple patches applied over CUPS UI) , or is
>> it a
>>>>> new behavior in CUPS 2.x?
>>>>> 
>>>>> --
>>>>> -Alex
>>>>> _______________________________________________
>>>>> cups mailing list
>>>>> cups at cups.org
>>>>> https://www.cups.org/mailman/listinfo/cups
>>>> 
>>>> _________________________________________________________
>>>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>>>> 
>>>> _______________________________________________
>>>> cups mailing list
>>>> cups at cups.org
>>>> https://www.cups.org/mailman/listinfo/cups
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> -Alex
>>> _______________________________________________
>>> cups mailing list
>>> cups at cups.org
>>> https://www.cups.org/mailman/listinfo/cups
>> 
>> _________________________________________________________
>> Michael Sweet, Senior Printing System Engineer, PWG Chair
>> 
>> _______________________________________________
>> cups mailing list
>> cups at cups.org
>> https://www.cups.org/mailman/listinfo/cups
>> 
> 
> 
> 
> -- 
> -Alex
> _______________________________________________
> cups mailing list
> cups at cups.org
> https://www.cups.org/mailman/listinfo/cups

_________________________________________________________
Michael Sweet, Senior Printing System Engineer, PWG Chair