holy moly - you're right! This fool will sleep so much better...a million thanks.On Thu, Dec 17, 2015 at 12:09 AM, Amber "Hawkie" Brown <hawkowl@atleastfornow.net> wrote:_______________________________________________I've ran into this before -- browsers sometimes rate-limit requests, and won't actually send the second request until the first is done, over the same connection, rather than making a second TCP connection -- try using cURL or wget, which has no such limitation, and see if it works any better.
> On 17 Dec 2015, at 08:11, Kevin Mcintyre <kebin70@gmail.com> wrote:
>
> Hey - I'm confused, so nothing new :) ...but I'm running at this example and I'm scratching my head.
>
> http://twistedmatrix.com/documents/current/web/howto/web-in-60/asynchronous-deferred.html
>
> I would've thought 2 requests could be served simultaneously, but when I fire off 2 requests the first received gets it's response after 5 seconds, while the second response takes 10 seconds.
>
> I think I understand what's happening, but I don't know why...and I would love an example where the subsequent request doesn't have to wait for the first request to finish.
>
> Thanks,
> Kevin
- Amber
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python
_______________________________________________
Twisted-Python mailing list
Twisted-Python@twistedmatrix.com
http://twistedmatrix.com/cgi-bin/mailman/listinfo/twisted-python