Hi Greg
Well the history of ETA changes might be useful but certainly is never
essential.
On 9 January 2015 at 17:30, Greg Young wrote:
> Its also very common to CALCULATE the ETA changes and raise them as events
> without necessarily persisting them.
>
> As a thought experiment if your notific
Its also very common to CALCULATE the ETA changes and raise them as events
without necessarily persisting them.
As a thought experiment if your notification system lost 1/1000 would
it really matter?
On Thursday, January 8, 2015 at 12:59:51 PM UTC+2, Tim Pigden wrote:
>
> Hmm - on reading o
On Thu, Jan 8, 2015 at 11:59 AM, Tim Pigden wrote:
> Hmm - on reading other threads and reflection I think I may have the wrong
> model here. The information about the ETA is possibly not something that
> should be persisted. It's not hard data. And perhaps my parcel should be
> split between a p
Hmm - on reading other threads and reflection I think I may have the wrong
model here. The information about the ETA is possibly not something that
should be persisted. It's not hard data. And perhaps my parcel should be
split between a persisting actor (still need 1m of them) and some sort of
