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

Harry Lewis harryl at us.ibm.com
Thu Aug 1 11:23:09 EDT 2002


No, it doesn't require the stated configuration... this is optional. 

Yes, of course... why else would I be suggesting it? Honestly, if so many 
people think it's a "bad" idea... let it go. 
---------------------------------------------- 
Harry Lewis 
IBM Printing Systems 
---------------------------------------------- 




"Robert Herriot" <bob at herriot.com>
Sent by: owner-ipp at pwg.org
07/31/2002 10:39 PM
 
        To:     Harry Lewis/Boulder/IBM at IBMUS
        cc:     "Hastings, Tom N" <hastings at cp10.es.xerox.com>, "McDonald, Ira" 
<imcdonald at sharplabs.com>, <ipp at pwg.org>, "'Mike Sweet'" 
<mike at easysw.com>, <Ron.Bergman at Hitachi-hkis.com>, "Ted Tronson" 
<TTRONSON at novell.com>
        Subject:        Re: IPP> Re: Last Call comment to remove redirect URL and status code from 
IPPGET

 

Am I correct in assuming that you are advocating this feature because IBM 
believes that it is useful and plans to support it in
some printer?
 
I had previously thought that you proposed the feature because you thought 
some unknown vendor might want the feature.
 
One downside of this feature is that it requires the printer to be 
configured to know about some notification server and it requires
an IPP notification server which may or may not be a printer. All this 
adds up to a more complex solution to deploy and to administer.
 
Bob Herriot
----- Original Message ----- 
From: Harry Lewis 
To: Robert Herriot 
Cc: Hastings, Tom N ; McDonald, Ira ; ipp at pwg.org ; 'Mike Sweet' ; Ron.Bergman at Hitachi-hkis.com ; Ted Tronson 
Sent: Wednesday, July 31, 2002 8:06 PM
Subject: IPP> Re: Last Call comment to remove redirect URL and status code from 
IPPGET


While I respect Bob's, Ira's, Ted's (and other's) opinions the 
conversation sure seems to have adopted an arbitrary tone w.r.t. to IPP 
bells, whistles and trinkets. If someone says they can use a simple 
feature like redirect I see no need to block it. If it were mind bending I 
would argue otherwise... but  redirect is quite simple by any gauge and 
doesn't even register on the scale of numbness many feel when first 
confronting IPP. 

Notification redirect should consist of writing the client to accept a URL 
(in place of the printer URL) where it should expect to find subsequent 
notifications. 

I can always feature the redirect... so I guess I'm going down for last 
count w/o a big struggle. I don't  think Bob is correct in attributing 
lack of chatter as lack of significance. I think the spotlight is off IPP 
and you are witnessing the polling interval. 
---------------------------------------------- 
Harry Lewis 
IBM Printing Systems 
---------------------------------------------- 



"Robert Herriot" <bob at herriot.com> 
07/31/2002 03:05 AM 
        
        To:        "McDonald, Ira" <imcdonald at sharplabs.com>, "'Mike 
Sweet'" <mike at easysw.com>, "Hastings, Tom N" <hastings at cp10.es.xerox.com> 
        cc:        Harry Lewis/Boulder/IBM at IBMUS, 
<Ron.Bergman at Hitachi-hkis.com>, "Ted Tronson" <TTRONSON at novell.com>, 
"McDonald, Ira" <imcdonald at sharplabs.com>, <ipp at pwg.org> 
        Subject:        Re: Last Call comment to remove redirect URL and 
status code from IPPGET 

 


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
>
>



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://www.pwg.org/archives/ipp/attachments/20020801/6b93e8ce/attachment-0001.html


More information about the Ipp mailing list