Really 64

- SubscriptionManager
- SubscribeAggregator
- ObjectSubscriber
- Replayer
- GorillaCenter new subsxription handling
- All the Gorilla wiring
- JSON parsing fix
- WIP of Unsubscribe handling
I am sure of that, you can test it too, the replayer send this message here 
```
def shutdownWithObjectSubscriptionAck(reason: String) = {
    shutdown(reason)
    objectSubscriber ! SubscriptionFailure(r, 500, reason)
  }
```
What happens here is, first the replayer will terminate and the `objectSubscriber` will receive terminate message as it watch the replayer and will enter this case which will send the first failure message to the client
```
case Terminated(actor) =>
      subscriptionFailed(505, "Associated replayer stopped")
``` 
In the second line you send `objectSubscriber ! SubscriptionFailure(r, 500, reason)` which will enter this case 
```
case SubscriptionFailure(r, errorCode, reason) =>
      subscriptionFailed(errorCode, "Internal Server Error")
```
and the client will receive the second message