This thread looks to be a little on the old side and therefore may no longer be relevant. Please see if there is a newer thread on the subject and ensure you're using the most recent build of any software if your question regards a particular product.
This thread has been locked and is no longer accepting new posts, if you have a question regarding this topic please email us at support@mindscape.co.nz
|
Is there any possibility to explicitly close a database connection? I mean without disposing UnitOfWork. P.S. The question is there for a possibility of taking the architecture path of WCF Data Transfer Objects to the client & statefull application server (BTW, there are some good articles on the topic in the new MSDN magazine), which means holding on to the domain model entities and UnitOfWork (even though we do understand the general idea and pattern of UOW being short-lived) at the application server to spare round-trips to the database. |
|
|
|
|
This isn't currently possible. It's something that has been requested a couple of times and is also relevant to rich client scenarios, but we have a trade-off to consider between providing this additional fine control and keeping the API abstract of the details of the database access, so we'd have some design to do before deciding to offer this feature. |
|
|
|
|
Hmmm... Let me ask this way. This means it is somewhere on your to-do list or still pointing-out reasons not to include it on that list? :)
|
|
|
|
|
It is a feature we know some people would like, but which we are dubious about offering. So it is on our "think about if people keep asking for it" list, not our "wish" list. Of your choices, I'd say we're in the "pointing out reasons not to include it on the to-do list" phase. *grin* |
|
|
|
