That's very possible. This problem occurs (mostly) with specific ajax calls on this web site. None of these calls *seem* unusual in terms of the information sent and information returned. Other ajax calls don't experience this nearly as often, but it still happens. Furthermore, we installed an older version of this web application earlier this year in another 2003 production environment, and never experienced these problems over there, but that machine is not one I can go and play with. This leads me to believe that it's a combination of something configurable in a 2003 server in addition to the semantics of the particular ajax call. The reasoning for these bizarre symptoms are beyond me, though.
--~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
