Thanks. I have been trying tcpdump sniffer in the server side, and discovered that the server always receives 80% of the byte content (I described it here: http://tinyurl.com/5rqfp5). This is very interesting, but unfortunately led me nowhere.
I don't manage to reproduce it, for over a year now, so I can't run a sniffer in the client. Also, this is a high capacity internet application, not intranet, therefore contacting the users even just for a question is rather difficult, let alone installing a sniffer in the client side. Amit On Dec 2, 11:40 am, Lothar Kimmeringer <[EMAIL PROTECTED]> wrote: > Amit Kasher schrieb: > > > Does anyone has any new insights about this issue? We've been > > investigating for over a year(!), and we seem to not be the only > > ones... > > >http://tinyurl.com/5rqfp5 > > I have no insights but what about firing up Wireshark and > protocolling the packets that are exchanged between client > and server. At the moment the problem occurs you should be > able to come up with the protocol of that specific HTTP- > session. Maybe that helps to track down where the problem is. > > Regards, Lothar --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to Google-Web-Toolkit@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
