Fiddler

What is Fiddler?

Fiddler is a Web Debugging Proxy which logs all HTTP(S) traffic between your computer and the Internet. Fiddler allows you to inspect all HTTP(S) traffic, set breakpoints, and "fiddle" with incoming or outgoing data. Fiddler includes a powerful event-based scripting subsystem, and can be extended using any .NET language.

For Detail: Fiddler Detail

Gmail

Gmail is the best application website i ever seen. Simple implementation, Super Ajax, Cute Chatting, Status Messages, Fast Mail Checking, Live updating and its features are endless as my wordpress database wont withstand

when you type: www.gmail.com, the following action will happen. See it is very interesting.
For Details View: Gmail Architecture

Flv Player

function createPlayer(theFile, arg)
{
var s = new SWFObject("Controls/mediaplayer.swf","thePlayerId","350","255","7");
s.addParam("allowfullscreen","true");
s.addVariable("file",theFile);
s.addVariable("width","350");
s.addVariable("height","255");
s.addVariable("wmode","opaque");
s.addVariable("autoscroll","true");
s.addVariable("allowscriptaccess","true");
s.addVariable("wmode","opaque");
s.addVariable("bufferlength","10");
s.addVariable("displayheight","230");
s.addVariable("allowfullscreen","true");
s.addVariable("autostart","true");
s.addVariable("shuffle","false");
s.addVariable("enablejs","true");
s.addVariable("javascriptid","thePlayerId");
s.write("divmsndbc"); }';

For Details View: flv video Playing videos with Flv Player

Load user data once with an HttpModule

A couple of years ago, when I was less focused, finished with my book and completely unmotivated to develop anything useful for my own non-day job projects, I struggled trying to shoehorn my apps into the ASP.NET Membership and Profile API's. Probably because of my lack of experience, I became very frustrated at the point where the objects started to relate to the data.

It occurred to me fairly recently that these systems provide a level of abstraction that makes sense in terms of data storage, but you still have to do a fair amount of work in your providers to make sure you aren't pounding the data store. That means caching, of course, but you still might be creating objects in several places (handlers, the page, user controls, etc.), and each time you're going to the well, whether it be by way of the caching mechanism you create or going to the data store.

So why cache at all? Why not get the data once, early in the request cycle, and go back to it when you need it? Oddly enough, it was good old fashioned FormsAuth that made me think of this, where in ASP.NET v1.x we would look up the user and roles, probably in an HttpModule, and access that data from where ever.

For Details View : http://www.uberasp.net/getarticle.aspx?id=51