You can use the "threaded" model. That would give you a unique instance for each thread (or web request if you're writing a webapp). HiveMind doesn't really inject the implementation object into other objects. It injects a proxy. The proxy will make sure it delegates to the appropriate implementation object based on the service lifecycle model.
On 10/20/06, Aj Gregory <[EMAIL PROTECTED]> wrote:
Is there some way to create a service-point so it will create a new
instance of an implementation class each time the service is injected
somewhere? Kinda the exact opposite of singleton.
Thanks,
-Aj
