I was browsing through the breed of IoC (Inversion of Control) Frameworks like PicoContainer & Spring.我翻阅品种间海洋学委员会（反演控制）框架一样， picocontainer ＆春天。 I have one simple question for the proponents of these frameworks.我有一个简单的问题，为倡议者，这些框架。

I come from the old camp where we merrily use我来自旧营地，我们merrily使用 Service Locator Pattern服务定位模式 for solving the same problems that IoC addresses.为解决相同的问题，国际奥委会的地址。 We face two typical problems in a Service Oriented Architecture .我们所面对的两个典型问题，在一个面向服务的体系结构 。

Assume that a service A (defined by the interface) is provided by B, C & D implementations.假设一个服务（所定义的接口）是由乙，丙＆ D的实现。 Assume that they all have registered.假定他们的所有已注册的。 Now I know that C is superior service provider than B. I also know that D is the best.现在我知道C是优越的服务提供商比乙我也知道， D是最好的。 However D may not be available at all times.但D在无法提供在任何时候。 So we may need to fallback on C, when D is unavailable.因此，我们可能需要后备的C ，当D是不可用。 My first simple question is how do you pass on this information in a distributed environment when each of these services are provided by different Service providers.我的第一个简单的问题是你怎么通过关于这方面的资料，在分布式环境下，当每一个提供这些服务由不同的服务供应商。 How do we, as a standard, address QoS rules?我们如何，作为一个标准，地址的QoS规则？

Now assume that each of these services have hot-swappable components.现在假设每个这些服务有热插拔组件。 B has E & F, D has H & J etc. We need to specify that in a generic fashion meta-data about the service addressing QoS and other concerns like specifying order or usage, graceful decline etc. B已E及F署署长已h生等，我们需要指定，在一个通用的时装元数据有关的服务，解决QoS的问题和其他问题一样，指定命令或使用，优美的下降等。

How does modern IoC frameworks address this?请问现代国际奥委会的框架解决这个？