Peter, just for the sake of completeness... Have you tried embedding an IFRAME within the 'outer' page, then rendering the frame content with a separate .aspx 'for one shot only', and setting a meta refresh (of 10 seconds, or less) on the iframe?
Often this works very well without flicker involved. I know it's a heresy to suggest this in the web 2.0 era but still... <sigh> it works, and is architecturally rather clean, so why not use it? -----Original Message----- From: Discussion of advanced .NET topics. [mailto:[EMAIL PROTECTED] On Behalf Of Peter Vertes Sent: Thursday, January 25, 2007 10:32 PM To: ADVANCED-DOTNET@DISCUSS.DEVELOP.COM Subject: Re: [ADVANCED-DOTNET] Streaming Data to a Webpage OK, thanks for clearing that up for me Peter. I'm looking at docs for the XMLHttpRequest object right now and it does look promising. Thanks for pointing me in the right direction. -Pete On 1/25/07, Peter Ritchie < [EMAIL PROTECTED]> wrote: > > Yes, that's wrong. You can use the XMLHttpRequest's open method to open a > connection to a URL (including port #) and wait for a response. The > default is to do it "asynchronously" (it's asynchronous to the client > code) and process state change via the onreadstatechange event [1]. See > http://msdn.microsoft.com/library/default.asp? > url=/workshop/author/dhtml/reference/methods/open.asp for the > documentation of the open method. > > see http://support.microsoft.com/kb/290591 for example of client accessing > classic ASP server (with implementation) with XmlHTTPRequest. > See http://support.microsoft.com/kb/893659 for example of client accessing > ASP.NET Web Service with XmlHTTPRequest. > > [1] http://msdn.microsoft.com/library/default.asp? > url=/workshop/author/dhtml/reference/properties/onreadystatechange_1.asp > > -- Peter [del] =================================== This list is hosted by DevelopMentor® http://www.develop.com View archives and manage your subscription(s) at http://discuss.develop.com
