Thanks for your comment. I actually have thought about this a lot but haven’t started implementing it yet because it is not trivial to put all my requirements together. My current idea would be to write most of it in Java and use Javascript only for the dynamic parts:

- BatchProcessor is used for multi threading.
- Recursion through all nodes (written in Java?). If you throw in multi threading you get the interesting problem that in some cases you don’t want to process children before the parent hasn’t been processed by another thread.
- Branching should be controlled ideally by Javascript evaluators for maximum flexibility (is it fast enough to call those often?).
- Transaction size should be configurable, so e.g. 100 documents can be updated in one transaction.
- Failover to single document transactions in case of an error would be great.
- The processing logic should either run as Javascript or run an arbitrary Action.
- The whole batch processing should be an Action itself so you can invoke it on the fly.

In projects I am currently only using recursive processing written in Java (single threaded) using batched transactions for larger updates.

I’m wondering who would be the best person at DevCon to talk to about this.

Basically I’m envisaging something similar to the Java BatchProcessor functionality [1] in the Alfresco API.

[1] http://dev.alfresco.com/resource/docs/java/repository/org/alfresco/repo/batch/BatchProcessor.html