Michael Schwarz wrote: > Thanks, I will have a look on it... > > Regards, > Michael > > > On 6/8/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > > > We are using .NET 1.1 as well. I'll try to recreate this example in a > > small project that I can send to you. > > > > Thanks, > > Jason > > > >
Michael, the answer seems to be the 10 second timeout period that is set in the core.js: timeoutPeriod: 10*1000, The calls that are having problems with take longer than 10 seconds, closer to 13-14. I did create a small project with an Ajax server side method that calls Thread.Sleep and that allowed me to zone in the 10 seconds before looking into core.js. I'm not sure what the difference is, but the timeout doesn't seem to happen in earlier AjaxPro versions. Again, we migrated yesterday from 5.11.24.1 (because we discovered the race condition problem happening) to 6.6.6.1 and then tried 6.6.7.1. I see in your change notes that in 6.6.2.1 you state that you changed the default value of AjaxPro.timeoutPeriod to 10 seconds. Is this overrideable in any way? It can't simply be changed per application because the core.js is a resource within the AjaxPro.dll. I wondering what the possibility is of creating a separate "configuration" file in javascript that would maintain constants that individual app developers could change, and then have the core.js file refer to those constants. Any thoughts? I'd start poking around to do that myself if I had the latest source for 6.6.7.1. Thanks for everything! Jason --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
