Hi, As far as I am concerned there are only 3 ways to manage the dep

[FeatureRequest] Fluent lifetime management about hypodermic HOT 1 CLOSED

ybainier commented on July 17, 2024

[FeatureRequest] Fluent lifetime management

from hypodermic.

Comments (1)

ybainier commented on July 17, 2024

Hey,
why don't you create a nested container per thread? Everything you resolve in the nested container will have the lifetime of the thread. It is already available and pretty simple.

This will give (maybe again sorry) you a look at the resolution mechanism:

class ThreadLocal
{
public:
    ThreadLocal(shared_ptr< Container >& container,
                shared_ptr< TransientDependency > transientDependency,
                shared_ptr< SingleInstanceDependency > singleInstanceDependency)
    {
        ContainerBuilder builder;
        builder.registerType< UnknownSingleFromTopLevel >().singleInstance();
        
        auto nestedContainer = builder.buildNestedContainerFrom(*container);
        m_worker = nestedContainer->resolve< Worker >();
    }
};

class Worker
{
public:
    Worker(shared_ptr< TransientDependency > transientDep,
           shared_ptr< SingleInstanceDependency > singleInstanceDep,
           shared_ptr< NotThreadLocalSingleInstanceDep > notThreadLocalSingleInstanceDep,
           shared_ptr< UnknownToTopLevelSingleInstance > unknownToTopLevelSingleInstance);
};

now the configuration:

ContainerBuilder builder;
builder.registerType< SingleInstanceDependency >().singleInstance();
builder.registerType< NotThreadLocalSingleInstanceDep >().singleInstance();

auto container = builder.build();

for (auto i = 0; i < 8; ++i)
{
   thread([=]() { container->resolve< ThreadLocal >(); });
}

SingleInstanceDependency and NotThreadLocalSingleInstanceDep will always be shared accross all threads because they are configured inside the toplevel container; that's true even if it is resolved by the nested container.
Worker and TransientDependency are transient by default, that is, a fresh instance is created everytime they are resolved.
UnknownToTopLevelSingleInstance cannot be known from the top level container. This could be the trick you need.

So I guess you could split the configuration like so:

extend ContainerBuilder for the components of the whole app
extend ContainerBuilder for the components that are supposed to be thread local. That way, everytime you instantiate a thread, you can create a nested container with these merged capabilities.

Am I missing something or does this achieves your goal?

from hypodermic.

Recommend Projects