This blog has personalition features for you, the reader. Below is a key of what all the icons mean and which aspects of the layout they change.
Close Window
I'm in the process of coming up with a little example that shows you how you can use the XMLHTTP ActiveX Object and ASP.NET to process long running tasks. I will post the code tomorrow.
Thursday, March 24, 2005 11:28 PM
Thanks for the warning.
I'm waiting.
First, I Hope that yuo speak in Spanish, because my english is terrible. [Spanish] Lei el articulo y basado en el implemente la misma estrategia en un aplicativo en ASP.NET. Este es el JavaScript checkStatus() function checkStatus() { createRequester(); if(req != null) { try { req.onreadystatechange = process; req.open("GET", checkStatusUrl, true); req.send(null); } catch(e) { alert("Error " + checkStatusUrl); } } } function process() { if(req.readyState == 4) { // only if "OK" if (req.status == 200) { document.location.replace(nextPageUrl); } } } /* Note that this tries several methods of creating the XmlHttpRequest object, depending on the browser in use. Also note that as of this writing, the Opera browser does not support the XmlHttpRequest. */ function createRequester() { try { req = new ActiveXObject("Msxml2.XMLHTTP"); } catch(e) { try { req = new ActiveXObject("Microsoft.XMLHTTP"); } catch(oc) { req = null; } } if(!req && typeof XMLHttpRequest != "undefined") { req = new XMLHttpRequest(); } return req; } La primer vez funciona perfectamente, pero si vuelvo a llamar la misma página web no invoca la pagina .ashx, pero el readyState entrega 4 y 200, como si hubiera sido existoso. ¿Alguna razón para tal comportamiento?
Hola, si l arazon es simple... CACHE :P tienes que controlar el cache del XMLHTTP (tambien tiene que ver con el Brorwser Cache) pero la solucion mas rapida es: crear un parametro que siempre cambie. Asi la URL que envias sera dirente siempre y siempre hara la conexion al server. Saludos
Fields denoted with a "*" are required.