On May 14, 6:33 pm, "Richard Brodie" <[email protected]> wrote: > "Tomas Svarovsky" <[email protected]> wrote in message > > news:[email protected]... > > > This is a good point, but then it would manifest regardless of the > > language used AFAIK. And this is not the case, ruby and php > > implementations are working quite fine. > > What I meant was: not reading the data and leaving the connection > open is going to force the server to handle all 100 requests concurrently. > I'm guessing that's not what your other implementations do. > What happens to the timing if you call response.read(), response.close() ?
Now I get it, but nevertheless, even when I explicitely read from the socket and then close it properly, the timing still doesn't change. Thanks for advice though -- http://mail.python.org/mailman/listinfo/python-list
