On 07/08/13 21:41, sebb wrote:
On 8 July 2013 20:46, Robert Burrell Donkin
<[email protected]> wrote:
<snip>
2. analyse this model against policies, building a strongly-typed, immutable
report model
Won't that require lots of memory?
Not sure about lots (the state required should be relatively small) but
yes, more
At present the source can be forgotten as soon as a match occurs.
Perhaps
An architecture where each document flowed through the system is likely
to be more efficient and easier to parallelism.
However, I think that the current streaming design isn't particularly
intuitive or obvious. I would be happy to retain an improved streaming
design.
Robert
