Wrap this up in some sort of unit of work, at both the List and the Store level

[xivSolutions]

No description provided.

[Assassyn]

I like the repository approach so the question is do you want to use unit of work exclusively or just as an option?

[xivSolutions]

I was wanting to have it available as an option. The way I've got it wired, one can use the store/list same as always (which I think is important), or aggregate them all into a Db which one can create a "context", do various work elements against one or more lists, and then "Commit." It's crude and messy yet though.

Any way we do this, though, adds complexity, since transactions need to succeed or fail (and rollback) at both the backing store and list level.

Also, updates are problematic, and changes made to individual items in a list can be observed and read by others before they are committed on the back-end. Solutions to this are also problematic.

I am torn here between maintaining the simplicity and implementing a proper unit of work.

This might be something to put on hold until later.