All these complicated caching and proxying won't be implemented unless
they work with Netscape Navigator, and Internet Explorer. If you guys
write to the same APIs as these browsers do, you don't have to worry
about these usage models, since they will have to accomodate you, rather
than vice versa.
Babak
>There are also alot of other issues that may come up and bite us when we
>start
>layering on top of HTTP, like caching, proxies, and security models. It
>may end
>up that the usage model of how HTTP is used for the majority of the
>industry
>(Web page browsing) may conflict with how we want to implement printing.
>I heard
>some very complicated usage models come up at the HTTP working group
>meeting in
>San Jose, with regards to caching and proxying. These algorithms and
>configurations
>may conflict with our simple requirements of submitting a print job and
>checking
>status.