I don’t cause teachers trouble;
My grades have been okay.
I listen in my classes.
I’m in school every day.
My teachers think I’m average;
My parents think so too.
I wish I didn’t know that, though;
There’s lots I’d like to do.
I’d like to build a rocket;
I read a book on how.
Or start a stamp collection…
But no use trying now.
’Cause, since I found I’m average,
I’m smart enough you see
To know there’s nothing special
I should expect of me.
I’m part of that majority,
That hump part of the bell,
Who spends his life unnoticed
In an average kind of hell.
- Profile your web page using tools like firebug
- Save images in the right format to reduce their file size
- Minification and bundling of CSS and JS :this will reduce size as well as number of http requests made
- Avoind inline CSS and JS as these are not cached .Putting in CSS and JS files enable it to be cached
- Use CSS sprites instead of images .This reduces the number of http requests made
- Use server-side compression to reduce file sizes
- Offload site assets and features ,Example , Use diffrent servers for Images
- Use Cuzillion to plan out an optimal web page structure
Weak references are all about garbage collection. A standard object will not “disappear” until all references to it are severed, this means all the references your various objects have to it have to be removed before garbage collection will consider it garbage.With a weak reference just because your object is referenced by other objects doesn’t necessarily mean it’s not garbage. It can still get picked up by GC and get removed from memory.
The managed heap contains two internal data structures whose sole purpose is to manage weak references: the short weak reference table and the long weak reference table. These two tables simply contain pointers to objects allocated within the managed heap.
Initially, both tables are empty. When you create a WeakReference object, an object is not allocated from the managed heap. Instead, an empty slot in one of the weak reference tables is located; short weak references use the short weak reference table and long weak references use the long weak reference table. Once an empty slot is found, the value in the slot is set to the address of the object you wish to track and the object’s pointer is passed to the WeakReference’s constructor. The value returned from the new operator is the address of the slot in the WeakReference table. Obviously, the two weak reference tables are not considered part of an application’s roots or the garbage collector would not be able to reclaim the objects pointed to by the tables.
Attack Surface Analyzer takes a snapshot of your system state before and after the installation of product(s) and displays the changes to a number of key elements of the Windows attack surface.
- Developers to view changes in the attack surface resulting from the introduction of their code on to the Windows platform
- IT Professionals to assess the aggregate Attack Surface change by the installation of an organization’s line of business applications
- IT Security Auditors evaluate the risk of a particular piece of software installed on the Windows platform during threat risk reviews
- IT Security Incident Responders to gain a better understanding of the state of a systems security during investigations
Below are the assumptions made when designing garbage collector in .Net framework ,which ended up in generations concept .
- The newer an object is, the shorter its lifetime will be.
- The older an object is, the longer its lifetime will be.
- Newer objects tend to have strong relationships to each other and are frequently accessed around the same time.
- Compacting a portion of the heap is faster than compacting the whole heap.
ASP.NET SignalR is a new library for ASP.NET developers that makes it incredibly simple to add real-time web functionality to your applications. What is “real-time web” functionality? It’s the ability to have your server-side code push content to the connected clients as it happens, in real-time.