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

Ted Tronson TTRONSON at novell.com
Wed Jul 31 12:45:34 EDT 2002


I originally declared that removing the redirect feature would be fine
for our IPP implementation as we are not currently doing notification
with our iPrint implementation.  

>From my point of view the only time that the redirect would be useful
is when the notification service is not running on the same box as the
print service.  Down the road if say the PSI group wanted to implement
some form of notification service it could be useful to just register
with one service that is remote from the target device or intermediary
device.  But, I'm With Ira on this.  I don't want to add any new
notification items to my client as we have shipped numerous Windows
clients at this point.  And, I don't have any users complaining that
they want to have notifications to annoy them.


Ted Tronson
Sr. Software Engineer
iPrint Engineering
801-861-3338
Novell, Inc., the leading provider of Net services software
www.novell.com

>>> "Robert Herriot" <bob at herriot.com> 07/31/02 03:05AM >>>
Harry says that redirect is simple to implement. I agree, but
implementation
is only part of the issue.
Each feature requires documentation, testing and support. There is no
such
thing as a free feature.

Very few people have responded to this issue and no one has said that
it is
a necessary feature.

So, it would seem hard to justify keeping a feature that.seems to have
no
value to anyone, but does have a cost to every vendor.

Bob Herriot

----- Original Message -----
From: "McDonald, Ira" <imcdonald at sharplabs.com>
To: "'Mike Sweet'" <mike at easysw.com>; "Hastings, Tom N"
<hastings at cp10.es.xerox.com>
Cc: "Harry Lewis" <harryl at us.ibm.com>; <Ron.Bergman at Hitachi-hkis.com>;
"Ted
Tronson" <TTRONSON at novell.com>; "McDonald, Ira"
<imcdonald at sharplabs.com>;
"Robert Herriot" <bob at herriot.com>; <ipp at pwg.org>
Sent: Tuesday, July 30, 2002 8:46 PM
Subject: RE: Last Call comment to remove redirect URL and status code
from
IPPGET


> 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