The question is, how much shared computation can be done
before dispatching to the individual services? Where rules
have common variables, it makes sense to share. If a common
variable can be introduced, through, for example, content
parsing, then it makes sense to expose this to the rule
evaluation engine.
Now, I further claim that services should be allowed to
introduce components that define and set variables for
the rule engine. An example is an XML parser. That
should be allowed to set variables like
"has-an-xml-phone-number-tag".
Hilarie
Markus Hofmann <hofmann(_at_)bell-labs(_dot_)com> 06/12/01 07:31PM >>>
Gamze Seckin wrote:
I guess streaming people already know that dynamic adjustments can be done
through the streaming server and there is actually no need for an
intermediary.
Sure, you can do all these dynamic adjustments within the service
module itself, which is a nice and simpler solution. The question is
whether we've to provide some (!) of this functionality in the OPES
devide (e.g. reflected in the rules) simply for performance reasons.
I agree that having all the dynamic stuff in the services themselves
is very attractive as it is simpler and cleaner - would be nice to
have. I'm just a little bit concerned that we might end up with a
system that simply lacks the required performance.
-Markus