title: How to implement two-phase commit in a .Net REST WCF service?
body: <p>I'm building RESTful web service, and I want to allow it to participate in distributed transactions.  </p>
  
  <p>An example scenario would be that my REST service might save a file on a server somewhere, and at the same time the caller marks this file as saved in its database.  However, if either the file server is full, or if his database call fails, the other action should not commit.</p>
  
  <p>What can I do to keep up my side of the bargain?  I'd like to find a solution that works for both .Net and Java clients.  I know it's a knotty problem, I was wondering if anyone had any tips or insights?  Thank you</p>