Thanks Daniel - appreciate the offer. My thinking currently is to have the "state" represented by the finite state machine, to be a number of different application variables. These variables should be encapsualed by an object which organises them into subsets - let's call these rule templates. The actual rules would be the values/ranges that one determines for the variables in the template.
The state changes being monitored would then apply to a ruleset, which encapsualtes a variable number of rules - which in turn define a set of values/range of values for the variables contained in the rule template. What this amounts to is a combination of finite state machine and a rudimentary rules engine. The developer would have to be able to set values for rules from the jsp and call the FSM state check mechanism. The FSM itself should obviously have a session lifespan. Given the above configuration, this mechanism could be used for anything, from worflow management, user profiling (eg. targeting of individuals based on demographics) through the application of business rules. Any ideas on how best to achieve this would be greatly appreciated. Regards Emile > > Ive done some game logic years back in mmbase that used fsm but these > days (and you model) would be > easer in MMBase. Once the model is done adding some function for it > would mean easy control over them from > your taglib set. Very interesing and i would not mind putting a few > days in to help you. > > Daniel. > > > >
