Multiple concurrent save operations

Hi,

We're developing a 'test player' that presents questions to the user awaits a response and then saves that response to the db.

It happens that when the user responds quickly to question after question, we get the error that the save operation failed because another was still in progress.

Is there a way to tell df to queue the operations and quietly handle the commits without throwing exceptions?

Thanks

And creating a new unitofwork will do just that?

We want to move on, because we are pretty sure the answer will be 'dumped' into a keyless (!) table without any issues. If an issue arises, it probably will be a connection issue, with which we will deal later, when we start thinking about offline scenarios where answers will be buffered till communications are restored.

It is more important that the user can progress to the next question and continue the test.

Thank you for your helpful responses so far.

Something like this should do it?
var uow = new TestUnitOfWork(new EntityManagerProvider<AdamMiloEntities>(), _testCache);

(The testcache analogous to IGlobalCache in TH, is something we need since we cache certain sets of data to (hopefully) improve performance and avoid async headaches).

Thanks again!



Edited by siko - 16-Oct-2012 at 9:26am

Nice work. Thanks.

Originally posted by siko   Have a background worker periodically find all the entities not in 'Unchanged' state, import those into the connected EM, set the state to Unchanged in the disconnected EM and execute commitasync on the connected EM." ...