Thanks for your response, Craig. If I understand correctly, the auto-open concern is an issue when the same channel is shared on different threads. This is only the case when you don’t need the proxy to keep specific context (such as security credential) on each call. I know the TypedFactoryFacility would be a solution for this, resolving the component at the exact moment it's needed, at the cost of making the code perhaps more complicated. But I don't know what you mean with Lazy<IService1>. I'm guessing it's not the lazy component registration capabilities. I searched around and found nothing. Can you elaborate a little on this?
On Jun 28, 9:03 am, Craig Neuwirt <[email protected]> wrote: > For some reason WCF penalizes you heavily if you let it perform auto-open. > In fact, everything becomes sequential and throughput drops dramatically. > Can you inject Lazy<IService1>, Lazy<IService2> to help mitigate your > concern. You can probably also use the TypedFactoryFacility and inject > Func<IService1>, Func<IService2> as well. > -- You received this message because you are subscribed to the Google Groups "Castle Project Development List" 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-devel?hl=en.
