Interested to Buy Any Domain ? << Click Here >> for more details...
Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 2015 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 object service? : Entity framework
How to use multiple submit buttons in asp.net mvc?
How can you return string result from Action in ASP.Net MVC?
what do you mean by table-per-type?
What is difference between viewbag and viewdata and tempdata?
what is linq to entities?
Do you know about the new features in asp.net mvc 4 (asp.net mvc4)?
What is ViewData and TempData in ASP.Net MVC?
List the new features added in .net framework 4.0.
Explain linq to entities? : Entity framework
How to Redirect Tracing to a File
Explain something about model, view and controllers in asp.net mvc?
Does .NET Framework support SAX?
What is entitytypes? : Entity framework
Is it possible to cancel filter execution?
