i have created one repeater and now i want to refresh that repeater after each 1 minute . blow is my code :

 <asp:Repeater ID="gvd" runat="server">

                <ItemTemplate>
                    <tr class="gradeA">
                        <td>
                            <asp:Label ID="lblcategory" runat="server" Text='<%#Eval("Firstname")%>'></asp:Label>

                        </td>
                        <td>
                            <asp:Label ID="lblcontent" runat="server" Text='<%#Eval("Lastname")%>'></asp:Label>
                        </td>

                     </tr>
                </ItemTemplate>

            </asp:Repeater>

It is give perfect output but now i want to refresh this whole repeater via javascript because using updatepanel it is increase the load on the server

so how can i do this via javascript?

i have created one repeater and now i want to refresh that repeater after each 1 minute . blow is my code :

 <asp:Repeater ID="gvd" runat="server">

                <ItemTemplate>
                    <tr class="gradeA">
                        <td>
                            <asp:Label ID="lblcategory" runat="server" Text='<%#Eval("Firstname")%>'></asp:Label>

                        </td>
                        <td>
                            <asp:Label ID="lblcontent" runat="server" Text='<%#Eval("Lastname")%>'></asp:Label>
                        </td>

                     </tr>
                </ItemTemplate>

            </asp:Repeater>

It is give perfect output but now i want to refresh this whole repeater via javascript because using updatepanel it is increase the load on the server

so how can i do this via javascript?

• javascript
• c#
• asp
• webforms

Share Improve this question Follow edited Mar 4, 2017 at 4:38 mason 32.7k1111 gold badges8383 silver badges126126 bronze badges asked Sep 4, 2014 at 12:13 user3997016user3997016 1

• Do not think of it as "refreshing the repeater". Think of it as refreshing the table, because the Repeater exists purely on the server side, the resulting markup is on the client. Anyways, many people are starting to shy away from "continuously poll server for updates" in favor of using new technology to push the updates from the server to the client. In the .NET stack, the technology for this is SignalR. You'll find that SignalR is much better than constantly polling the server, lightening strain on the client, on bandwidth, and server resources. – mason Commented Sep 4, 2014 at 16:15

Add a ment  | 

3 Answers 3

Sorted by: Reset to default 5

SignalR was created to solve exactly the problem you are describing.

Here's your situation: You want a way to display information that could change constantly. At any point, the most up to date information should be displayed.

A Web Forms centric approach would be to use an UpdatePanel. But myself and some others don't really like those. They usually cause problems later on down the road, because they don't play well with other technology. They're also "expensive", they send a lot of data back and forth between the client and server, using up bandwidth and resources.

Another approach, somewhat touched on by deostroll, is to use AJAX to poll the server at a regular interval for the data. This isn't a bad approach, though I would not have implemented it the way he did. His/her way would be a massive drain on bandwidth and resources because you're recreating the entire table every few seconds. Boiled down to a conversation type format, his/her approach look like this:

Client -> Server - Send me the entire table.
Server -> Client - Here's a 1MB table.
Client -> Server - Send me the entire table.
Server -> Client - Here's an 1MB table.
Client -> Server - Send me the entire table.
Server -> Client - Here's a 1.5MB table.
Client -> Server - Send me the entire table.
Server -> Client - Here's a 1MB table.

Instead, an AJAX polling based approach should look like this:

3:30PM Client -> Server - The last data I have is from 3:30PM. Got anything new?
3:30PM Server -> Client - No.
3:31PM Client -> Server - The last data I have is from 3:30PM. Got anything new?
3:31PM Server -> Client - No.
3:32PM Client -> Server - The last data I have is from 3:31PM. Got anything new?
3:32PM Server -> Client - No.
3:33PM Client -> Server - The last data I have is from 3:32PM. Got anything new?
3:33PM Server -> Client - Yes, two new records. Here you go, 10KB.
3:34PM Client -> Server - The last data I have is from 3:33PM. Got anything new?
3:34PM Server -> Client - No.

That uses much less bandwidth. I'm not going to bother showing you how to do it in code, though understand it's relatively straightforward and represents a massive improvement over deostroll's approach.

Instead, I want to describe how a SignalR based approach would work. SignalR is "real time". It takes advantages of several techniques for "pushing" changes from the server to the client. One technology used to implement this is called web sockets, which is the preferred method. But if the client or server isn't capable of web sockets, SignalR gracefully switches to other techniques. You don't have to worry about that though, it's all taken care of for you.

Let's look at a simple way to implement this in SignalR. Every time you change the table data, you want to run a JavaScript function on the clients to update them with the latest data.

First, we need a hub on the server.

public class TableHub : Hub
    {
    }

On the client side, do this to wire up an event:

 $(function () {
    var tableHub= $.connection.tableHub;
    tableHub.client.tableChanged= function (html) {
    //append the html markup to your DOM
    };
});

Then whenever the table data changes, call this code on the Server:

var context = GlobalHost.ConnectionManager.GetHubContext<TableHub >();
string html="<table><tr><td>Some data</td></tr></table>"; //obviously you'd built the HTML table up here
context.Clients.All.TableChanged(html); //call tableChanged() on the client!

That will actually end up calling the tableChanged() function on the client side in near real time, initiating it from the server side! That's basically Remote Procedure Call. So not only is this taking care of selecting the best available transport mechanism (web socks, Server Sent Events, Long Polling) but it resolves client side functions and lets you call them by using dynamics on the server side.

That was a very basic example. We're sending the entire HTML for the table down, which isn't ideal. But, with a little work you could have the client notified of when to make an AJAX call to an API to retrieve only the changed table data, instead of retrieving the entire table. In fact, that's an approach I took on a website I recently created to push new articles from the server to the client in real time.

Based on your rep and profile, I don't believe you'd catch all this fast. You really need to explore if you want to know why we are doing it this way.

You need some javascript of the style as mentioned in the answers already here. You need to do some ajax calls to a page/generic handler (ashx) to generate repeater markup.

There are several ways to render a control (i.e. a repeater), but for your case its best using a usercontrol to do that job. And that has certain challenges (not explaining why though).

Here is the generic way of doing just that alone - rendering a user control - using a generic handler

public class refresh : IHttpHandler
{

    public void ProcessRequest(HttpContext context)
    {
        context.Response.ContentType = "text/plain";
        context.Response.Cache.SetCacheability(HttpCacheability.NoCache);
        FormlessPage page = new FormlessPage();
        Control ctrl = page.LoadControl("~/RepeaterHoster.ascx");
        StringWriter sw = new StringWriter();
        HtmlTextWriter hw = new HtmlTextWriter(sw);
        page.Controls.Add(ctrl);
        page.RenderControl(hw);
        context.Server.Execute(page, hw, false);
        context.Response.Write(sw.ToString());
    }

    public bool IsReusable
    {
        get
        {
            return false;
        }
    }
}

You'd notice I've used a Formless page. That is defined as follows:

public class FormlessPage : Page
{
    public override void VerifyRenderingInServerForm(Control control)
    {
        //keeping it empty

        //base.VerifyRenderingInServerForm(control);
    }
}

Then your aspx page can look like this:

<%@ Page Language="C#" AutoEventWireup="true" CodeBehind="WebForm1.aspx.cs" Inherits="WebApp.DynamicRepeater.WebForm1" %>

<%@ Register Src="RepeaterHoster.ascx" TagName="RepeaterHoster" TagPrefix="uc1" %>

<!DOCTYPE html>

<html xmlns="http://www.w3/1999/xhtml">
<head runat="server">
    <title>Repeater Refresh Demo</title>
    <style>
        #content {

            border:1px dotted;
            line-height:2em;
        }

            #content div {

                background-color:#00ff90;
                padding:3px;
                display:inline;
                margin:3px;
                text-align:center;

            }
    </style>
    <script src="Scripts/jquery-2.1.1.min.js"></script>
    <script>
        $(function () {
            var content = $('#content');
            setInterval(function () {
                content.load('refresh.ashx');
            }, 5000);
        });
    </script>
</head>
<body>
    <h2>Repeater Refresh Demo</h2>
    <form id="form1" runat="server">
        <div id="content">
            <%-- content here (in this div) refreshes every 5 seconds--%>
            <uc1:RepeaterHoster ID="RepeaterHoster1" runat="server" />

        </div>
    </form>
</body>
</html>

The user control is fairly very simple for illustration purposes. I am just showing 5 product names at random from db (northwind) - mdf file. There is nothing significant in its code behind hence omitting that one.

<%@ Control Language="C#" AutoEventWireup="true" CodeBehind="RepeaterHoster.ascx.cs" Inherits="WebApp.DynamicRepeater.RepeaterHoster" %>
<asp:Repeater ID="Repeater1" runat="server" DataSourceID="SqlDataSource1">
    <ItemTemplate>
        <div>
            <%# ((System.Data.DataRowView)Container.DataItem)[0] %>
        </div>
    </ItemTemplate>
</asp:Repeater>
<asp:SqlDataSource ID="SqlDataSource1" runat="server" 
    ConnectionString="<%$ ConnectionStrings:NorthwindDB %>" 
    SelectCommand="SELECT TOP (5) ProductName FROM [Alphabetical list of products] ORDER BY NEWID()"></asp:SqlDataSource>

Now, why exactly are we doing all this? Why not simply use a repeater control instead of a user control?

Well, if you truly want to know, you'd really want to figure all this yourself. :)

Happy programming...

setTimeout(functionName, milliseconds) will set a specific function to run after the {milliseconds} argument.

You can just have, at the end of that refresh function, a call to setTimeout(refreshFunction,60000)

You can also use the method __doPostBack('UpdatePanel1', ''); to update the panel in that refresh method.

So your code might look like:

function() RefreshPanelEveryMinuteLoop {
    __doPostBack('UpdatePanel1', '');
    setTimeout(RefreshPanelEveryMinuteLoop, 60000);
}