Hi, Ajax.NET Professional has a configuration for a timeout period (AjaxPro.timeoutPeriod) on client-side JavaScript. If your request needs more than this duration a timeout function can be called, but the original request has been aborted already. In the current release you can return true/false wether the request should be aborted or not. See the example at http://munich.schwarz-interactive.de/default.aspx.
If you are running Fiddler you may see the result comming correct from the web server. The problem here is that the connection from the web browser has aborted, and you see only the response made to the proxy server (Fiddler). You should use tools like Ethereal that capture the real http traffic. There you will see that the request is aborted. Regards, Michael On 6/15/06, abesh <[EMAIL PROTECTED]> wrote: > > The fix given above needs a change on client machine. > so this can't be a solution, is any one know to work around this? > > Thanks, > > > > > -- Best regards | Schöne Grüße Michael Microsoft MVP - Most Valuable Professional Microsoft MCAD - Certified Application Developer http://weblogs.asp.net/mschwarz/ http://www.schwarz-interactive.de/ mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ajax.NET Professional" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/ajaxpro The latest downloads of Ajax.NET Professional can be found at http://www.ajaxpro.info -~----------~----~----~----~------~----~------~--~---
