Order of discarding of threaded services when there is dependency beetwin them

[Aleksej]

Lets say I have 2 threaded services, and one of them is must be created 
before other AND discarded after it. One service must wrap other in 
time. Idea is to create database connection service
and transaction service. Transaction service is wired with database 
connection and at the end of thread it must commit or rollback all 
changes. But because there is no order of discard specified, it is 
possible, that Hivemind first will discard connection service and then 
will try to discard transaction service, which will try to 
commit/rollback using already closed connection. Any 
ideas/recomendations/tricks  how to solve such problem?

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]