Hi Tom,
Yes, this is an issue. I think we can now eliminate the requirement that
printers must support ippget wait mode, and make it a suggestion.
Marty
"Hastings, Tom N" <hastings at cp10.es.xerox.com>@pwg.org on 07/27/2001
05:39:38 PM
Sent by: owner-ipp at pwg.org
To: Michael Sweet <mike at easysw.com>
cc: Marty Joel <mjoel at netreon.com>, ipp at pwg.org
Subject: RE: IPP> Duplicate ippget events
Michael wrote:
Even with the multipart encoding, I think there will still be a
significant number of implementations that don't implement the
event wait mode.
Currently, the spec REQUIRES that a Printer that supports ippget Delivery
Mode, MUST support the Event Wait Mode. Is this an ISSUE?
Tom
-----Original Message-----
From: Michael Sweet [mailto:mike at easysw.com]
Sent: Friday, July 27, 2001 16:57
To: Hastings, Tom N
Cc: Marty Joel; ipp at pwg.org
Subject: Re: IPP> Duplicate ippget events
"Hastings, Tom N" wrote:
> ...
> However, remember this problem is only for using Get-Notifications
> in Event No Wait mode (polling). For Event Wait mode, there aren't
> any duplicate events returned to a Notification Recipient. If we
> think that the majority of use will be with Event Wait Mode, then we
> don't need to solve the problem for Event No Wait Mode.
Even with the multipart encoding, I think there will still be a
significant number of implementations that don't implement the
event wait mode, and if we don't provide a way for clients to
specify what they've already seen then the efficiency of ippget
in this mode will be quite poor.
--
______________________________________________________________________
Michael Sweet, Easy Software Products mike at easysw.com
Printing Software for UNIX http://www.easysw.com