|
From: Olivier J. <oli...@pc...> - 2004-09-10 07:19:26
|
katentim @hotmail.com wrote: > There's also a question of handling errors without transactions in LDAP. > > Would the implementation be to throw something like > DataAccessException and just roll back other transactional resources? I was thinking about this, indeed. Should we try to simulate transactions by, for instance, storing the reverse delta of what we're actually performing so that a rollback could go back ? It still isn't a good solution as it doesn't preserve the isolation property of transactions. It can still help in some situations. Else, we can do the contrary and only stores changes on a commit, while intercepting calls to ldap function to overwrite the result by our temporary transaction data. The naive, non transactional, approach seemed the most natural to me as we don't "pervert" the nature of ldap storage and let the developer chooses his data support knowing its strengths and weaknesses. Still, if there is a need for something more sophisticated, I'll be glad to try my best to incorporate it. Regards Olivier |