IPP> RE: Last Call comment to remove redirect URL and status code from IPPGET

IPP> RE: Last Call comment to remove redirect URL and status code from IPPGET

IPP> RE: Last Call comment to remove redirect URL and status code from IPPGET

McDonald, Ira imcdonald at sharplabs.com
Tue Jul 30 23:46:06 EDT 2002


Hi,

If we keep it, remember it can be OPTIONAL to use but MUST be REQUIRED
to support (for the Client - that is, IPP Clients MUST honor and use
the redirect).

Does everyone want a new REQUIRED to implement application redirect
feature (for IPP Clients)?

I doubt it very much.  And that's the test that the IESG will apply,
for interoperability.

Cheers,
- Ira McDonald


-----Original Message-----
From: Mike Sweet [mailto:mike at easysw.com]
Sent: Tuesday, July 30, 2002 9:09 PM
To: Hastings, Tom N
Cc: Harry Lewis; Ron.Bergman at Hitachi-hkis.com; Ted Tronson; McDonald,
Ira; Robert Herriot; ipp at pwg.org
Subject: Re: Last Call comment to remove redirect URL and status code
from IPPGET


Hastings, Tom N wrote:
 > ...
 > Could the six commenters (see the To: line) who agreed to remove
 > redirection, please respond as to whether they are still in favor of
 > deleting the Get-Notifications redirection or that they are now
 > willing to keep Get-Notifications redirection in the IPPGET spec in
 > case someone wants to implement IPPGET with a Notification Server.

If we keep it, we probably do need a redirect timeout parameter, or
to define what should happen if the redirect server doesn't handle the
notification...

 > As Bob asks, is anyone planning to use a Notification Server or think
 > that they might want to?

We're not planning to.

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



More information about the Ipp mailing list