Recently I read about a feature available in the .NET frametwork 2.0 or later that allows you to write transactional code blocks: that is, code blocks in which you can execute some actions or change the state of some objects and then, if something goes wrong, have the entire changes reverted to the initial state. The objects are taken to the state before the start of the transactional blocks and any other changes you performed are rolled back. The article is here.
Reading this got me thinking about how can I implement this in Java. I formulate the problem as it follows: “How transparent for the user can one implement transactional code blocks?”. Please note that I don’t say “Can you…” but “How transparent…”. I believe that allowing any amount of stress for the user, you can implement anything. The question is, how transparent and easy to use can one do it. Read the rest of this entry »
In the project that I am currently working I am implementing the OAuth protocol, in order to have the client and the server authenticate and exchange access tokens, before allowing the client to get access to the protected resources. Currently we are developing only the 2-legged model of OAuth (since we don’t need the resource owner authentication and permission allowance), but it is very likely that in the future we will switch to the 3-legged model.