Is the lack of deterministic destruction in .NET a problem

Question Posted / kirti

1 Answers
1931 Views
I also Faced
E-Mail Answers

Is the lack of deterministic destruction in .NET a problem..

Answer / 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

More Dot Net Framework Interview Questions

differences between poco, model first and data first approach?

0 Answers Microsoft,

What is a serverside technology? what is a clientside technology? what is a clientserver technology? what is a internet based application? what is a intranet based application? what is a windows application? what is a console application? Difference between console application and windows application?

4 Answers IBM,

What is domain class model?

0 Answers

Difference between .NET & J2EE

1 Answers

How does work clr?

0 Answers

How do you do role based security ?

1 Answers Accenture, BirlaSoft,

What is the necessity for singning an assembly with a strong name?

1 Answers L&T,

Can you use Razor code in Javascript in ASP.Net MVC?