aggregate_version optional

[hallgren]

It would be nice to have the option not to set a aggregate_version number when an event is created on an aggregate. The result would be that no version check is made when the event is stored. It would open up the possibility to have multiple threads doing writes at the same time on the same aggregate not get concurrency errors. It would be ok to not have the latet version of the aggregate loaded but still do writes.

[jesjos]

An event that doesn't bump the aggregate version, should it be allowed to have attribute deltas? I'm thinking a sloppy event store implementation may cause chaos by emitting non-versioning events with deltas.

[hallgren]

I'm thinking the event store should bump the aggregate version internally when the event is stored.

transacton start
  get lastest event
  bump aggregate version with last events aggregate version +1 
end of transaction

It will probably be used when no state changes are made in the aggregate.

Side note:
It would be nice to be able to send the read aggregate version and make a check that not the same attributres are changed in events between the read one and the events that is stored.