Sorry, to say it again, but you are talking here of a protocol between X
and Y without having modelized X and Y. The callout protocol, X and Y
modelization must be an harmonious interative process.
At 19:51 25/03/03, Alex Rousskov wrote:
On Tue, 25 Mar 2003, The Purple Streak, Hilarie Orman wrote:
> In my previous note I left out the rule that makes the stream
> restartable ... if stream A is "copy" and the callout server
> signals "no further copy", the easiest way to proceed with "no copy"
> mode is for the OPES processor to open a new stream, B, with the
> directive "this is the no-copy continuation of stream A". Anything
> un-acked on stream A is now sent on stream B.
>
> This does mean that "copy" streams cannot be multiplexed on a single
> reliable connection unless the callout server promises not to switch
> to "no-copy" mode.
You seem to be solving a very different problem.
modelize what you are talking about.
Could you please give an example or a use case?
examples are too specific and involving to many aspects.
The must be used to build and check a model. Not to
replace it.
It seems to me that you are trying to
introduce some negotiation here (callout server tells the processor to
copy/move, and the processor may copy/move in response). That could be
a useful feature _on top_ of the basic mechanisms we are trying to
finalize in this thread.
Sure he is. But what are you both really calling a "processor"?
> I'm still wondering how useful this will be; I'd always assumed that
> the intelligence about which parts to forward would reside with the
> OPES processor, or that the directives would be at a higher semantic
> level.
We may be talking about different use cases here. See my earlier
response to Abbie Barbir with specific examples I have in mind.
The callout server may modify the message.
what do you call the message? If it received only a part of the
stream, do you call message the chunk it receives or a set of
copied and non copied data chuncks. Dispatchers rules may
say that (A+B ) calls for B only to be modified into B', and that
(A+B' ) calls for A to be modified too, or in conjunction with B'.
Thus, the resulting data
stream from the callout server to the OPES processor consists, in
general, of new and old data chunks. The copy mode is meant to reduce
the number of old data chunks, nothing else.
Copying seems hazardous anyway because if several services are called in
conditional succession, how will a service know the nature of what is in
the buffer. Are they original or already modified data.
jfc