Using new sip-core with Saxon replacing the memory-leaking JDK XPath implementation
Making configuration lazy as we don't need it necessarily
Keeping track of domains previously known

If a domain has vanished from the configuration, which may in fact be due to a crash (e.g. timeout in relation to mongodb lookup timeout), we display an error instead of redirecting.
Merge branch '13.06-memory-leak' of github.com:delving/culture-hub into 13.06-memory-leak
Fixing processing for large sets

It appears that MongoDB has very slow writes (108 ms / record locally) with the FsyncSafe WriteConcern. I suppose this is new in the 2.4 series of MongoDB, as it wasn't the case earlier on. This caused a congestion in the processing pipeline which eventually leads to an out-of-memory error. I am now relying on MongoDBs claim that records will eventually get written from memory to disk.

Additionally, there's now a concrete number displayed next to the progress bar.
Merge pull request #949 from delving/13.06-memory-leak

13.06 memory leak