When I joined in has as a software engineer, one of my first mentors was Prabath Siriwardena. Although it was just 5-6 months in his team, I learnt a lot from him, ranging from writing good code to, team work. He recently acquired his MSc in computer Science from the University of Moratuwa. and today works at WSO2 in the open id integration team. You can listen to his pod cast on Open id here, in this talk he mentions about what open id tries to solve and it's advantages.
This is a post about object finalization in .NET. Finalization is not as inexpensive as we think, it increases the pressure put on GC.All objects that need finalization are moved into a finalizable queue and the actual finalization happens in a separate thread. Because the objects full state may be needed, the object itself and all the object it points to are promoted to the next generation (this is needed so that GC does not clean these objects off in the current round), and these objects are cleaned up only after the following GC. Due to this reason, resources that need to be released should be wrapped in as small a finalizable object as possible, for instance if your class needs a reference to an unmanaged resource, then you should wrap the unmanaged resource in a separate finalizable class and make that a member of your class and furthermore the parent should be a non-finalizable class. This approach will assure that only the wrapped class (class that contains the unmanaged resourc...
Comments
Post a Comment