On Mon, 7 Apr 2003, jfcm wrote:
On 19:09 07/04/03, Alex Rousskov said:
OCP does not distinguish between application message header and
application message payload. OCP treats the entire message as an
opaque sequence of octets. Should we explicitly state that "header"
and "payload" are not visible to OCP?
YES. Everything which clarfy what we talk about is an absolute need.
Will do.
Data seems appropriate. However this remark seems of interest to quote.
In the Minitel X.25 system for example I am investigating, the size of the
Message may be of interest if it is smaller than the X.15 window size. It
may make the transfer extremely fast.
OCP can relay OCP application message size via size parameter and
input/output application message size via meta-data. I am not sure how
your remark relates to OCP though. Please clarify.
Application connections are out of OCP scope. Should we state that
explicitly?
ABSOLUTELY. For the same reasons.
Will do.
There are no OPES connections, but Hilarie is probably talking about
OCP connections. Abbie suggests to rename OCP connections to
"sessions". Which term would you prefer?
Would these sessions represent the whole message transiting through
OCP towards as many services as required ? If yes I would accept the
concepts. Interaction otherwise? A session would be all the OCP
interactions that a message may perform from the dispatcher to
services until sent to the user. So you could talk of the OPES
session. Makes sense in French, but I do not know if it is the same
in English.
If "many services" are on different callout servers, then your
definition of "session" makes sense, but seems to be out of OCP scope
since OCP is concerned with single processor - single server
communication. If the services are on the same callout server, then
your "session" would be in OCP scope. It would be something that may
cross OCP connections even. I am not sure why we would need it though.
To be able to abort easier?
You sure you want to use OPES Processor the way you do?
For me it is opposed to every standard thinking I know.
Not sure what you mean. OPES processor is just an application proxy
that outsources processing of some messages. Sounds pretty "standard"
to me. Is it not?
Thank you,
Alex.