Loggerithim IS Alive

While Brenley napped today I eliminated some cruft from what will become the new Loggerithim. No longer will it centrally try and schedule and execute jobs. There are perfectly good systems for that sort of thing already.

This also eliminates a messy side problem. I had envisioned that Loggerithim's users would be able to create their own 'sensors' for collecting and storing quanta. Need to monitor your applications throughput? No problem, just add a Sensor and a Check. The Check sets up when to run the Sensor, which was to be a Java class. Enter Problem^tm. What if that involved a JDBC driver? Suddenly we need to load it. That's messy. A more reasonable solution is to facilitate outside clients to send data to use. I've got a couple ideas for just how to do that. JMS came to mind first, but I quickly decided against it because I don't want to force people to write there sensors in Java.

A side concern is how to verify that the thing sending quanta should be sending quanta. I, again, have some ideas.

Just to show it works, here is the test chart from the ChartBuilderTest testcase. This example is generated from mock data inserted 'realistically' into the mock DAO implementation.