Is the lack of deterministic destruction in .NET a problem
Answer Posted / kirti
It's certainly an issue that affects component design. If you have objects that maintain expensive or scarce resources (e.g. database locks), you need to provide some way for the client to tell the object to release the resource when it is done. Microsoft recommend that you provide a method called Dispose() for this purpose. However, this causes problems for distributed objects - in a distributed system who calls the Dispose() method? Some form of reference-counting or ownership-management mechanism is needed to handle distributed objects - unfortunately the runtime offers no help with this.
| Is This Answer Correct ? | 0 Yes | 0 No |
Post New Answer View All Answers
What is MVVM design pattern?
What is the greatest advantage of using asp.net mvc over asp.net webforms?
What is the difference between windows vista and .net framework 3.0 ?
What is meant by bootstrap in mvc5?
What is definingquery in entity framework? : Entity framework
Why is the .net framework 3.0 a major version number of the .net framework if it uses the .net framework 2.0 runtime and compiler?
how do you query in entity model when the result has a join from from different database other than the entity model?
What is edm designer? : Entity framework
What is rxjava used for?
what do you mean by navigation property?
What is an asynchronous controller in asp.net mvc?
what is entity data model?
How do you assign a value to a complex number 7 how has exception hand changed in .net framework 4.0?
What is ViewData and TempData in ASP.Net MVC?
What is the difference between model view and controller?