IPP> NOT - IPPGET Delivery Method - ISSUE 02 'ippget' URI

IPP> NOT - IPPGET Delivery Method - ISSUE 02 'ippget' URI

Mike Sweet mike at easysw.com
Thu Oct 25 20:46:05 EDT 2001


McDonald, Ira wrote:
> ...
> So let's just say that methods that are client pull (not server
> push) MUST NOT specify "notify-recipient-uri" in the Subscription
>  attributes group.
> 
> OK?

No argument here.

> PS - Recall that we can tell if IPPGET is supported (even though
> it MUST NOT appear in 'notify-uri-schemes-supported') because of
> 'operations-supported'.

Right, but that doesn't tell us what operation to use for a
specific subscription, right? :)

Currently we can say that if there is no notify-recipient-uri,
then use IPPGET and Get-Notifications for the subscription, but
what about other methods that might need the same treatment?

I know I'm nitpicking, but we need to make sure that the spec
addresses these issues so that future extensions (and there *will*
be more extensions I'm sure) can work together and not confuse
clients...

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




More information about the Ipp mailing list