Re: [google-appengine] Re: IE/Opera + Dev Server = slow, problematic

2012-11-26 Thread Brian Quinlan
Hi Kaan, On Fri, Oct 12, 2012 at 6:20 AM, Kaan Soral wrote: > I just had this idea now, If there is any http headers or modifications that > will prohibit IE/Opera from making async requests we may try those. (Make > responses HTTP 1.0 etc.) It should be a not so hard modification on maybe > dev_

[google-appengine] Re: IE/Opera + Dev Server = slow, problematic

2012-10-11 Thread Kaan Soral
I just had this idea now, If there is any http headers or modifications that will prohibit IE/Opera from making async requests we may try those. (Make responses HTTP 1.0 etc.) It should be a not so hard modification on maybe dev_appserver.py or other files that prepare the response Any ideas? O

[google-appengine] Re: IE/Opera + Dev Server = slow, problematic

2012-10-10 Thread Adam Lofting
I've been suffering with the same experience testing App Engine in IE running on Windows 7. Weirdly it runs fine in IE Tester (all versions), which has been my solution for now. On Monday, September 24, 2012 2:38:16 AM UTC+2, Kaan Soral wrote: > > I can't use IE or Opera for testing with dev

[google-appengine] Re: IE/Opera + Dev Server = slow, problematic

2012-09-25 Thread Kaan Soral
Thanks for the suggestion Bryce -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/_x_9v9sn-fAJ. To post to this group, send email to google-appengine

[google-appengine] Re: IE/Opera + Dev Server = slow, problematic

2012-09-25 Thread Bryce Cutt
Correction: The necessary argument is --address=0.0.0.0 On Monday, September 24, 2012 12:20:14 PM UTC-7, Bryce Cutt wrote: > > I have seen this before and I believe it is due to the browser making > multiple parallel connections to the dev server. The dev server only > supports a single connect

[google-appengine] Re: IE/Opera + Dev Server = slow, problematic

2012-09-24 Thread Bryce Cutt
I have seen this before and I believe it is due to the browser making multiple parallel connections to the dev server. The dev server only supports a single connection at once so some/many of these connections will time out or just fail. It is worse if you have multiple browsers making requests