In another word, on what ground does a ICAP client decide to use
preview or not to use? Should we use the not-yet-standardized OPTIONS
method to find out?
Yes, you should. This is just the thing the OPTIONS response is made
for. In the Network Appliance implementation, headers in the OPTIONS
response indicate whether preview is supported and the size of the
preview.
It's important that headers like these get rolled back into the ICAP
standard to foster interoperability among clients and servers.
Jeff
-----Original Message-----
From: Yang, Lily L [mailto:lily(_dot_)l(_dot_)yang(_at_)intel(_dot_)com]
Sent: Thursday, May 31, 2001 9:37 AM
To: 'Markus Hofmann'
Cc: ietf-openproxy(_at_)imc(_dot_)org
Subject: RE: iCAP Issues at OPES Workshop
I have a simple question about the preview mode in ICAP -- it seems to me
that preview is service dependent or even server implementation depedent,
i.e., some servers may support it since it makes sense to that particular
application, some may not. How does the ICAP client figure this out? In
another word, on what ground does a ICAP client decide to use preview or not
to use? Should we use the not-yet-standardized OPTIONS method to find out?
Lily
-----Original Message-----
From: Markus Hofmann [mailto:hofmann(_at_)bell-labs(_dot_)com]
Sent: Friday, May 25, 2001 9:02 AM
To: OPES Group
Subject: iCAP Issues at OPES Workshop
All,
as you might have seen on the agenda for the OPES Workshop, well have
a session on iCAP implementations and open issues with the current
iCAP document.
If you've done any iCAP implementation and would like to share your
experience in a 5 minutes talk at the Workshop, please let me know.
Also, please post any comments/suggestions/open issues you have found
with the current iCAP draft to the list PRIOR to the OPES Workshop.
We'd like to compile a list of such issues and discuss them at the
Workshop. Jeremy will lead a session on this, so please provide some
input.
Thanks,
Markus