Suggestion box

In order of priority :)

#1. Show how to implement support for promotable single phase enlistments.

#2. Show how to build a volatile compensator that is able to run user code at rollback.

#3. Show how to use DependendentTransaction in a multi-threaded environment.

I got another one to add - Something that clearly explains nested transaction scopes.

Okay one more - Something that explains Serialization level setting in TransactionScopeOptions in a non-database setting.

BTW I got a Q 4 U which I have gotten conflicting answers to. In Sql Server 2005, with two databases involved, what is the serialization level that the transactions are run on? (Assuming that the suggested serialization level using TransactionScopeOptions was ReadCommitted).

Thanks for all your help :)

- SM
PS: I wrote this up - http://www.codebetter.com/blogs/sahil.malik/archive/2005/04/28/62604.aspx - might be incorrect, but would love comments, or maybe the suggestion #1 above will subsume it.

Sahil, for #1 you can take a look at http://blogs.msdn.com/florinlazar/archive/2005/05/17/418595.aspx

Jim-- could you spin up a post explaining System.Environment.FailFast and when it is appropriate to use this mechanism? I'm particularly curious about its usage with respect to building reliable systems.

Thanks Florin. I saw that, you have a fantastic blog I must add.

http://pluralsight.com/blogs/dbox/archive/2005/04/30/7880.aspx said that I should file my grievance with you. We wish that more of the API would provide delegate based extension (eg, like Ruby blocks).

Thanks!

Jared,

As Don pointed out, that set of choices was one that we agonized over repeatedly when building System.Transactions. It's a great topic to dive into. I'll plan to do up an entry on this -- what we were balancing, what an ideal answer might look like, and generally how we thought about it.

Jim.