Re: OCP questions

[Alex Rousskov <rousskov@xxxxxxxxxxxxxxxxxxxxxxx>]

On Wed, 16 Apr 2003, jfcm wrote:

> Most of the points risen here would get a clear response with a
> simple diagrams such as :
>
> http  | data input | dispatcher | call-out protocol | server | call-out
> protocol | data-output | http
> <------ OPES ?
>          <------ OPES ?

We already have/had such diagrams. Obviously, they did not provide
enough "clear responses". Note that OCP has nothing to do with "http |
data input |" and "data-output | http" parts. OCP Core has specific
wording about that. That wording replaced some of the figures that had
those parts in earlier OCP Core versions.

> PS. What about protocol conversion, is that OPES?

It can be. An application proxy that does protocol conversion may
support OPES mechanisms and may be OPES-compliant. A decent HTTP proxy
today has to convert between HTTP and FTP (or even Gopher, WAIS,
etc.). I do not see why OPES proxies should be more limited than
existing HTTP proxies. If OCP is involved in protocol conversion, OCP
agents would have to negotiate/agree on how to specify
original/adapted protocols via application message metadata.

Alex.