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.
<mike@easysw. To: Carl Kugler/Boulder/IBM@IBMUS
com> cc: email@example.com
Sent by: Subject: Re: Re IPP NOT - 9 issues in the IPPGET spec.htm
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
> desirable, otherwise you can only send a single notification per
> 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 firstname.lastname@example.org Printing Software for UNIX http://www.easysw.com
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 17:18:48 EDT