Thanks for the explanation Chris.
I'm not sure I'm knowledgable enough about IoC and DI to make the call whether having a container that takes parameters on a Resolve call is a good thing or not. The reason I'm pursuing this is that one of the libraries I'm working with is built to be
"container aware" but requires the container adapter to support resolving with parameters.
Recently I've been surveying the available containers out there and I thought that AutoFac's method of supporting parameters is really neat. They use delegates that represent a factory for a given dependency. The cool thing is that if your "service"
that fulfills a dependancy has additional parameters the container will attempt to autowire them in. In this way the client can still use the known factory delegate and pass in some known parameters and defer the rest of the dependencies to the container.
In my opinion this is much nicer than the key/value property bag approach that Castle Windsor (and other containers, I think) uses.
Anyways, I may dig into it a bit, but thanks again for the explanation.