> > > What do you mean by data driven? > > > It may be appropriate for UT::Session to act like a generic machine. > > If the machine treats the data it's given as instructions, it can do a > > lot more with less code.
> Er, I am not entirly with you here. I think it sounds a little > dangerous as I can't be sure what is being passed to the Session by > the clients. That is why I have the added Event layer. It's not dangerous if you plan it carefully... Your tone suggests that you may possibly be about to dismiss what could easily become one of your most powerful programming techniques -- because it's "dangerous." If you can't be sure what's being passed to the Session by clients, on a per-transaction basis, that's fine. But you *can* be sure that whatever gets passed to Session matches one of a finite number of patterns, otherwise it's an error. Don't let your data box you in! :-) Remember, YOU are the programmer. L8r, Rob
