Jason Clawson

Objects no longer have to implement Serizalizable to be capable of being serialized in hazelcast. For example: ``` hazelcastConfig .getSerializationConfig() .addSerializerConfig( new SerializerConfig().setTypeClass(TaskStatus.class).setImplementation( new TaskStatusSerializer(smileMapper)) ) ```

Register TaskResponseListener to be able to listen to responses from across the cluster via the DistributedFutureTracker.onMessage. This could also be where we could implement issue #9 "Support task retry"

If a task throws a specific exception, allow it to be retried up to a defined number of times Can rely on issue #24 in order to implement. The downside...

Hazelcast allows you to write custom low-level distributed services. Lets take advantage of that to allow distributing a task in the same call as writing to the write ahead log....

Its just better

If a worker has nothing to do, it should immediately try and find more work to do instead of waiting for the rebalance task to fire

- Only expose one generic type to the developer using TaskBatchingService.... the item type. - Create an interface to represent the return type from HazeltaskInstance with only 4 methods: startup(),...