View Complete Post
I want to have a code that would establish connection from the server to the jQuery client, to update the front page of the website, when some new data is added to the DB. I of course could have an ajax call from the client on every second to check up the database for any changes, but I am just wondering if there is any way to establish a connection from the server side to the client.
The perfect solution would work like that:
- when the page is open, the client registers itself on the server for changes
- the server (knowing all the registered clients) prompts all of them when a change is done
- if any of the clients does not respond, the server removes the client from the registered list
- clients, update the page contents with the new data from the server
The question is if it is possible? Again, I could make all the clients reconnect to the server every second using ajax, however, this does not seem like a clean solution, and additionally it would put an unnecessary load on the server (e.q. 100 clients requesting update every second).
Thanks in advance,
Jozef A. Habdank
Is it possible to handle the same event in more than one client without using Remoting or WCF? In my test example I have 2 console apps and a class library all in the same solution. The event lives in a Singleton class in the class library and
both console apps have a reference to the dll and have handlers for the event. I have the 2 console apps set as multiple startup projects; however the event appears to only be firing to the one that is "active". If I could get confirmation on whether
what I'm trying is not possible (or whether I'm going about it the wrong way) it would be much appreciated.
AJAX is meant to go beyond mere partial page rendering. Find out where Dino Esposito thinks dynamic pages are headed in the future with ASP.NET AJAX.
MSDN Magazine June 2008
Microsoft AJAX Library and the ASP.NET 2.0 AJAX Extensions provide a number of compelling features ranging from client-side data binding, to DHTML animations and behaviors. Learn all about them here.
MSDN Magazine January 2007
This month Dino Esposito dissects the client-side source code generated by ASP.NET pages.
MSDN Magazine December 2006
MSDN Magazine February 2004
MSDN Magazine January 2004
In the September and October 2000 issues of MSDNÃÂ® Magazine I discussed how to build a client-side environment for ASP applications; that is, a serverless environment to run ASP pages (see Cutting Edge: A Client-side Environment for ASP Pages and Cutting Edge: A Client-side Environment for ASP Pages-Part 2).
MSDN Magazine January 2003
In the past, Web developers often used ActiveX controls if they wanted customized client-side functionality incorporated into their Web applications. Now, they can build objects supported by the Microsoft .NET Framework which are more compact, lightweight, secure, and seamlessly integrated. By hosting .NET Windows Forms controls in Internet Explorer, developers can realize many of their client-side Web development goals. This article adapts ActiveX concepts for use with Windows Forms, and builds a multifile upload application that demonstrates these techniques.
MSDN Magazine January 2002
MSDN Magazine December 2000
MSDN Magazine October 2000
MSDN Magazine September 2000