There are a few problems with the DbClientTrasactionPlayer? and Log.
Firstly, they both deal with XML directly, rather than a more abstract
Transaction data structure. This creates a dependency on XML parsers and
makes it more difficult to generalize the code to interpret the
transactions, since most of the "state" transactions have two distinct and
nearly incompatible forms: a direct form with a tag that is the name of the
transaction and one that uses the "invoke" tag. Second, the usage of a
client interface and a transaction log/player should be extended to other
modules (really just the constraint engine).
Original issue reported on code.google.com by miata...@gmail.com on 15 Sep 2009 at 4:06
Original issue reported on code.google.com by
miata...@gmail.comon 15 Sep 2009 at 4:06