IPP Mail Archive: IPP> Re: Re IPP NOT - 9 issues in the IPPG

IPP Mail Archive: IPP> Re: Re IPP NOT - 9 issues in the IPPG

IPP> Re: Re IPP NOT - 9 issues in the IPPGET spec.htm

From: Carl Kugler (kugler@us.ibm.com)
Date: Tue Jul 31 2001 - 17:17:05 EDT

  • Next message: Hastings, Tom N: "RE: IPP> NOT - ISSUE 05 [return successful-ok-events-complete']"

    You're right, I forgot about that. For no-wait-mode you don't need
    multipart. But it is critical for wait-mode if we are going to send
    complete application/ipp responses for each part, since the version,
    status, and request-id are positional fields.

         -Carl

                                                                                                                               
                        Michael Sweet
                        <mike@easysw. To: Carl Kugler/Boulder/IBM@IBMUS
                        com> cc: ipp@pwg.org
                        Sent by: Subject: Re: Re IPP NOT - 9 issues in the IPPGET spec.htm
                        mike@easysw.c
                        om
                                                                                                                               
                                                                                                                               
                        07/31/2001
                        03:02 PM
                                                                                                                               
                                                                                                                               

    Carl Kugler wrote:
    >
    > IPP Mail Archive: Re: IPP> NOT - 9 issues in the IPPGET specMS> I think
    > event-wait-mode should be OPTIONAL but RECOMMENDED. There
    > will always be client and server implementations that can't do the
    > multipart encoding, or can't spare the extra socket resources.
    >
    > Even when event-wait-mode is false, I think multipart encoding would be
    very
    > desirable, otherwise you can only send a single notification per
    operation,
    > even if several are waiting to be delivered. This is a lot of overhead,
    > especially if persistent connections aren't used.

    But (unless I read it wrong), the current spec allows the printer
    to send multiple event notification groups in a single response,
    so you can get all your events even without multipart encoding
    (for the no wait mode, anyways)

    --
    ______________________________________________________________________
    Michael Sweet, Easy Software Products                  mike@easysw.com
    Printing Software for UNIX                       http://www.easysw.com
    



    This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 17:18:48 EDT