On 19:51 26/03/03, Alex Rousskov said:
> I think that the comment below refers to applying dispatch rules to
> the result of a dispatch. I.e., assume the content is two parts,
> {A,B}. That content triggers a modification to part B, resulting in
> {A,B'}. The dispatch rules applied to {A,B'} trigger a modifiction to
> A, resulting in {A',B'}.
OK. This seems to have nothing to do with OCP. This is about rule
processing, right?
No. the question was about a message definition and copying.
I say you have two chuncks A and B. What may make or not
one single message.
(In between you responded that the message definition was
application dependent - what I have to digest as not my own
thinking).
The first dispatch rule leaves A untouched, so A can be sent.
Now the second rule says that A is to be modified.
I did not say where the second dispatch rule is applied.
It can be on a cascading dispatcher or a loop back into the
first dispatcher before sending. Depends on the modelization.
Where am I to find A depending on the cases?
- it may have been sent - if there are considered as 2 messages
- it may have been copied to a server and not returned since unchanged
- it may have been copied back
- it may not have been copied to the precedeing service
I do not think it is complex but it needs to be made clear.
Because we may certainly find cases where it is complex.
jfc