Is the lack of deterministic destruction in .NET a problem
- 1 Answers
- 1217 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
List the new features added in .net framework 4.0.
Explain representational state transfer (rest) in detail?
What are advantages of Dependency Injection (DI) in ASP.Net MVC?
how do you query in entity model when the result has a join from from different database other than the entity model?
What is storage model? : Entity framework
what is conceptual model?
Which version of .net framework is installed?
Explain the advantages and disadvantages of ASP.Net MVC over ASP.NET?
Is http stateful or stateless?
What is RouteConfig.cs in ASP.Net MVC 4?
What is model first? : Entity framework
i want to take the fast track training on >net Frame work and work flows and share point could you tellme the good institutes for that cources
what is entityclient?
What is associationset? : Entity framework
Can I remove .net framework?
