Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 1552 Views
- I also Faced
- E-Mail Answers
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 page life cycle?
what is .edmx file and what it contains?
what is explicit loading?
What is a model in programming?
What are actions in asp.net mvc?
What is connected scenario? : Entity framework
How we can register the Area in ASP.Net MVC?
What are the levels at which filters can be applied in an asp.net mvc application?
Explain the advantage of packaging over xcopy in .net?
What are actions in mvc?
What is Layout in ASP.Net MVC?
How to change the action name in ASP.Net MVC?
What is disconnected scenario? : Entity framework
What is the mvc pattern (model view controller pattern)?
What is ViewData and TempData in ASP.Net MVC?
