Question: Let's take a **really simple example** on using jQuery to ajaxify our page...

```
$.load("getOrders.aspx", {limit: 25}, function(data) {
    // info as JSON is available in the data variable
});

```

and in the ASP.NET (**HTML part**) page *(only one line)*

```
<%@ Page Language="C#" AutoEventWireup="true" 
         CodeFile="getOrders.aspx.cs" Inherits="getOrders" %>

```

and in the ASP.NET (**Code Behind**) page

```
public partial class getOrders : System.Web.UI.Page
{
    protected void Page_Load(object sender, EventArgs e)
    {
        string lmt = Request["limit"];
        List<Orders> ords = dll.GetOrders(limit);

        WriteOutput( Newtonsoft.Json.JsonConvert.SerializeObject(ords) );
    }

    private void WriteOutput(string s) 
    {
        Response.Clear();
        Response.Write(s);
        Response.Flush();
        Response.End();
    }
}

```

**my question is**

Should it be 

```
protected void Page_Load(object sender, EventArgs e)

```

or

```
protected void Page_Init(object sender, EventArgs e)

```

So we can save some milliseconds as we don't actually need to process the events for the page, or will `Page_Init` lack of some sorting of a method by the time it is called?

**P.S.** Currently works fine in both methods, but I just want to understand the ins and outs of choosing one method over the other

Answer: 
Basic page life cycle will answer your question Full article : <http://www.codeproject.com/KB/aspnet/ASPDOTNETPageLifecycle.aspx>

![alt text](https://www.codeproject.com/KB/aspnet/ASPDOTNETPageLifecycle/9.jpg)

check same question answer : [Page.Request behaviour](https://stackoverflow.com/questions/2719554/page-request-behaviour/2719588#2719588)
Page life-cycle only has meanings in context of page elements (controls), so i don't see any differences in your case, since you don't have any other child controls in your page - this is totally irrelevant.

But here is the real question: if you don't have any rendering of html in your page (only data serialization), why you have choose to work with regular .aspx page? 

Web service is ideal candidate for this scenario. And you'll be surprised how much performance improvement you'll gain in the end.