> At one time, people were proposing some kind of dispatching or routing IPP
> Object that would receive IPP requests and route them based on the embedded
> "printer-uri".
I was one of those people suggesting demultiplexing/dispatching,
but only within an HTTP server environment. As such, the server-
side component (CGI script, servlet, etc) would use the HTTP
header component to discriminate the real target.
> But the final decision was that the HTTP Request-URI and the embedded
> "printer-uri" MUST be the SAME. Therefore the IPP Object that receives
> the request must be the target.
Did we actually come to a final decision? I didn't read that we had.
(Maybe I'm missing a message or two on this subject?)
> There could be a problem if a proxy rewrites the Request-URI in any way.
Yeah, this worries me, too. We definitely need some serious
implementation experience to better understand the ramifications
of this situation.
...jay
----------------------------------------------------------------------
-- JK Martin | Email: jkm@underscore.com --
-- Underscore, Inc. | Voice: (603) 889-7000 --
-- 41C Sagamore Park Road | Fax: (603) 889-2699 --
-- Hudson, NH 03051-4915 | Web: http://www.underscore.com --
----------------------------------------------------------------------