David, Jay proved to me that the web-server was working with an experiment involving Apache Bench (ab); which is a nifty tool, I must say!
I'm still no wiser as to why the browser serialises GETs to a single server. Hypothetically, if I wanted to AJAX the replies from my script into two divs -- I need to know why it's taking me 2·n seconds, and not just n. On Tuesday, 28 April 2015 13:09:54 UTC+1, David T. Pierson wrote: > Rather than expect a single browser instance to open separate > simultaneous connections to your server, make it easier on yourself and > use separate browsers or even separate machines to issue the requests. My original experiment already involved two windows and a degree of hand-eye coordination developed over years of TF2 play. More machines would have been too much for me to handle. Fact is, I was so disappointed that Racket wasn't performing (apparently), that I forgot to do good science to find out why. > Or even script the requests using a separate Racket instance! :-) Or even that! Tim -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to racket-users+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
