Ignore:
Timestamp:
Dec 20, 2011, 2:19:43 PM (12 years ago)
Author:
Jessica B. Hamrick <jhamrick@…>
Branches:
no-cups
Children:
ef8df33
Parents:
6effd50
git-author:
Jessica B. Hamrick <jhamrick@…> (12/20/11 14:19:43)
git-committer:
Jessica B. Hamrick <jhamrick@…> (12/20/11 14:19:43)
Message:

Fix bugs; can now again do 'lpq' and get back a reasonable response

File:
1 edited

Legend:

Unmodified
Added
Removed
  • server/lib/gutenbach/server/requests.py

    r6effd50 rcad7502  
    125125    @handler_for(const.Operations.GET_PRINTER_ATTRIBUTES)
    126126    def get_printer_attributes(self, request, response):
     127        """RFC 2911: 3.2.5 Get-Printer-Attributes Operation
     128
     129        This REQUIRED operation allows a client to request the values
     130        of the attributes of a Printer object.
     131       
     132        In the request, the client supplies the set of Printer
     133        attribute names and/or attribute group names in which the
     134        requester is interested. In the response, the Printer object
     135        returns a corresponding attribute set with the appropriate
     136        attribute values filled in.
     137
     138        For Printer objects, the possible names of attribute groups are:
     139       
     140        - 'job-template': the subset of the Job Template attributes
     141          that apply to a Printer object (the last two columns of the
     142          table in Section 4.2) that the implementation supports for
     143          Printer objects.
     144
     145        - 'printer-description': the subset of the attributes
     146          specified in Section 4.4 that the implementation supports
     147          for Printer objects.
     148
     149        - 'all': the special group 'all' that includes all attributes
     150          that the implementation supports for Printer objects.
     151       
     152        Since a client MAY request specific attributes or named
     153        groups, there is a potential that there is some overlap. For
     154        example, if a client requests, 'printer-name' and 'all', the
     155        client is actually requesting the 'printer-name' attribute
     156        twice: once by naming it explicitly, and once by inclusion in
     157        the 'all' group. In such cases, the Printer object NEED NOT
     158        return each attribute only once in the response even if it is
     159        requested multiple times. The client SHOULD NOT request the
     160        same attribute in multiple ways.
     161
     162        It is NOT REQUIRED that a Printer object support all
     163        attributes belonging to a group (since some attributes are
     164        OPTIONAL). However, it is REQUIRED that each Printer object
     165        support all group names.
     166
     167        """
     168
    127169        # this is just like cups_get_default, except the printer name
    128170        # is given
Note: See TracChangeset for help on using the changeset viewer.