Thanks for the suggestion. For the most part, I can't install a packet sniffer into the clients network/machine. However, I did install a couple of tools into the browser (firebug being the main one) and I do see that the response is at least registering with firebug.
It's just not evaluated or throwing an error. I guess my next step is to start putting in debug statements everywhere I think the path might be breaking.... Thanks for the idea. I always wonder about how other people debug hard issues that can't be replicated in a controlled environment. Chris.... On Jul 31, 12:25 am, Joe Cole <[email protected]> wrote: > If you can, install ethereal (it has a new name) on the client and > monitor your server logs at the same time. That usually helps in > issues like this. > > Joe > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" 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/Google-Web-Toolkit?hl=en -~----------~----~----~----~------~----~------~--~---
