Imagine a sophisticated website: a fancy navigation system, menu, footer, language selection, logo, tabs... The page weighs a whole lot as it is and, on top of that, we have to reload the contents of the one and only drop-down list from our database. What does that mean to our ASP.NET application? First, a query sent to the server, then the processing and sending of the response to the browser, where the time-consuming page rendering process will take place. Up to several tens of seconds (!) to only to reload the values of a single drop-down list? It does not have to be that way because this is where Remote Scripting, which is basically a way of remote procedure calling on a server, comes in.