Yes, seems that since the server is single threaded and Chrome likes to
keep a connection open for further requests (when loading a lot of
small images at least), the server hangs until Chrome lets go of the
connection. I could verify this by reloading an image while the server
hangs, and that
Tried including Connection: close header in dev_appserver replies,
but at least that didn't help.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to google-appeng...@googlegroups.com.
To unsubscribe from
Use firefox ;-)
On Nov 1, 3:18 pm, Bemmu bemmu@gmail.com wrote:
Tried including Connection: close header in dev_appserver replies,
but at least that didn't help.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group,
Thanks. Decided to move small images to another server, that seems to
make it much less likely that Chrome would try to keep the connection
open.
--
You received this message because you are subscribed to the Google Groups
Google App Engine group.
To post to this group, send email to
Both sides of a TCP/IP connection can decide to close a connection.
The other side has to deal with it.
Or maybe an intermediate router decides to terminate it for some reason.
It should be possible to rewrite the dev-server to close the
connection once it has sent the responds.
Maybe the
Hi
You are using python 2.6, I suggest you retry using the supported
python2.5.x
Also the SDK is single threaded so everything will block whilst a
large request is processed.
Rgds
T
On Oct 31, 11:37 pm, Bemmu bemmu@gmail.com wrote:
The dev server often hangs. It seems to especially hang
On Sep 3, 1:58 pm, Harry glazed...@gmail.com wrote:
Hi,
I'm using an open source video player for playing uploaded video files
(via Blobstore).
If video file is small (less than a megabyte), it serves properly.
But when the file is larger, it crashes the development server.
Do I need to
