I had some time to look at the new code. Unfortunately the issue presented in my first post is still present. Thinking about it though, this is a case that can't be easily solved. Probably a two stage commit would be able to handle this properly, IF the workhorse is implemented in an aditional "prepare for commit" stage (i.e. the resource is pushing the data in a temp remote container in the "prepare for commit" stage and the "commit" afterwards is just performing a switch remotely to make the data available for retrieval by others).
I would love to hear your thoughts about this. -- You received this message because you are subscribed to the Google Groups "Castle Project Users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/castle-project-users?hl=en.
