Hi Samira,
DI has by nature some constraints, one is its memory leaks another one is the time of instanciation... I can keep going with some others like memeory consumption and not thread safe.
Servers technologhies are, starting by the historical one DI-Server and its companion which is B1WS and finishing by one which is the way to go: B1if (you can call scenario as web services).
What I meant by implementing a connection's cache mechanism, is to limit the number of connections and deconnections (the main issue with DI-API), but definitively I would try to go outside of this... But this is my personal point.
Regards,
Eric