IPP> Re: Why not use URI for Jobs?

IPP> Re: Why not use URI for Jobs?

IPP> Re: Why not use URI for Jobs?

Robert Herriot Robert.Herriot at Eng.Sun.COM
Tue Sep 2 16:50:17 EDT 1997


I think that the decision on Job-URI versus Job-Id all boils down to a
decision about one of two directions:


   1) The solution should solve today's problems easily while potentially
   making tomorrow's problem harder.


   2) The solution is allowed to make today's problems harder to solve in
   order to allow for the possiblity that tomorrow's problems be
   easier to solve.


I favor direction #1 which implies Job-Id because I believe that new
technology is most successful when it carries along existing technology
easily.  I also believe that it is not wise to make solving existing
problems substantially harder in order to achieve a payback that is not
well understood and may never happen. In my experience, when a feature
is added for some poorly understood future requirement, it is frequently
never used.


Bob Herriot






> From cmanros at cp10.es.xerox.coM Sat Aug 30 05:22:08 1997
> 
> OK,
> 
> ask Bob Herriot from Sun or Scott Isaacson from Novell about the details.
> 
> I have actually asked that somebody posts a reply to Randy's comments, so
> that we can get the thing out of the world.
> 
> Carl-Uno
> 
> At 10:20 PM 8/29/97 PDT, you wrote:
> >> I tried to sell exactly the compromise that you just suggested in your
> >> previous message, but people who are closer to implementation told me that
> >> it would not work.
> >
> >Am I still toe-ing the line if I ask you who they are, so I can ask them
> >why it won't work? It would be good to get this resolved to the point
> >that there aren't any technical questions about it being the right path,
> >and I can't figure out why it doesn't work.
> >
> >That is, there are two gateway cases:
> >  LPR client -(gw)-> IPP printer
> >      new printer, just support LPR too
> >      If you really need to map, well, you have to make up
> >      LPR job IDs and keep track of the ID->URL mapping, but
> >      it's a small table.
> >
> >  IPP client -(gw)-> LPR printer
> >      make Job URLs of the form "http://printer/LPRJOBNUMBER/nnnnn"
> >      where nnnnnn is the LPR job number.
> >
> >This doesn't need any auxiliary tables.
> >
> >Larry
> >
> >
> Carl-Uno Manros
> Principal Engineer - Advanced Printing Standards - Xerox Corporation
> 701 S. Aviation Blvd., El Segundo, CA, M/S: ESAE-231
> Phone +1-310-333 8273, Fax +1-310-333 5514
> Email: manros at cp10.es.xerox.com
> 



More information about the Ipp mailing list