-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Thread safe invocations #238
Comments
There is a workaround solution that already implemented. It might give an idea. |
Unfortunately it won't work for me. |
This might also help: http://blog.stephencleary.com/2012/02/async-and-await.html |
Thanks for the replay, however I'm not sure It would help me. As I see it the problem lies within the Castle project. When I browsed the source code I saw the Proceed method of AbstractInvocation. inside this method the Is there any particular reason not handling the Thanks |
Having recently reviewed #428 and #429, which also involve I think the solution should be to get rid of |
I'm voting to close this issue. While We should probably invest in thread safety some more for DP vNextMajor, but that is a different project from this issue (despite its title). If noone disagrees, I'll close this in a few days' time. |
Hello,
I wanted to create an "async shell" for methods to run asynchronously.
I created an AsyncInterceptor which look like this:
Unfortunately, it didn't work. For some reason the interceptor was called much more than once.
By looking at AbstractInvocation I saw the Proceed method is not thread safe ( Mostly the usage of currentInterceptorIndex ).
I wonder if there is anyway to support this kind of behavior.
Thanks,
The text was updated successfully, but these errors were encountered: