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.