Hi Krzysztof & friends,
I've been struggling a number of hours with a bug that we are having with interceptors calling IInvocation.Proceed() on a background thread. Then I found out this issue: http://issues.castleproject.org/issue/DYNPROXY-173 If it is indeed by design that interceptors must not call the invocation on a background, I strongly suggest that you actually check this (by means of registering the current Dispatcher in the invocation or whatever). The current behavior makes it too easy to shoot myself in the foot... :-) Ideally, I would see Martin's fix merged into Castle proper. I think it would be good to support this. Given that applications are written with more and more parallelism and asynchrony, I think it's not at all far-fetched to try and support these scenarios as best as we can in Castle Core. Best regards, -- -- -- -- -- -- -- -- PER LUNDBERG Software Engineer [email protected] <mailto:[email protected]> www.ecraft.com <http://www.ecraft.com/> tel. +358 (0) 20 759 8687 eCraft Oy Ab, Wolffskavägen 36, FI-65200 Vasa -- 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.
