Currently a c.i.p.process.model.ResultBlock contains a collection of
ResultItems (which are enriched key/value pairs).
In the context of remote request/response interactions, current implementations
first parse the response (e.g. a SOAP XML or so) and transform it into a
collection of ResultItems.
This has 2 disadvantages :
- in high-throughput systems, the DB becomes the bottle-neck due to a huge nr
of inserts
- we don't have a formal audit-trail of the actual requests and responses
We would like to introduce a system where it can be configured to alternatively
store the raw data as sent/received, and do the parsing on-demand when needed
(in memory).
Original issue reported on code.google.com by erwin...@gmail.com on 31 Jan 2014 at 9:16
Original issue reported on code.google.com by
erwin...@gmail.com
on 31 Jan 2014 at 9:16