On Thu, 15 Jul 2004, jfcm wrote:
I fully agree with Alex: there will be no drastic change in OCP and
P etc. But this will not be OPES and there will be impossible
problems of interoperation with the interconnected interapplications
- as mentionned above.
I am not sure I have the energy to debate abstract "what is OPES?"
questions, but I do want to make sure that there are no "impossible
problems" with specific solutions we develop.
Can you give a specific example of an impossible technical problem?
Not a vague problem of "what do we call it?" or "who consented to this
change?", but a specific technical problem? An example where a working
system is badly broken by introduction of OPES-compliant SMTP
adaptations...
Just one small question. Let assume a change is conditional to time.
What is the time we chose as a reference. The time the mail was
entered, the time it was sent, the time it reached each OPES filter,
the time it reached every OPES filters, do we take into account the
time the first mail or the last mail reached the filter? Let assume
a very common case : authority changes at a given time (a different
watch, a justice decision, etc.) and also the management rules.
It would be up to the rules author what time to use, on a per-message
basis, I think:
if (system.time() > 15:30) { ... }
if (message.ua_sent_time() < 13:10) { ... }
if (random() > 0.5) { ... }
Are all valid P statements, triggering OPE adaptations. Where is an
"impossible [technical] problem" here?
Thanks,
Alex.