Thanks, thats what I eventually found out. On Tuesday, February 23, 2016 at 12:39:00 PM UTC, jonah wrote: > > Hi Miguel- pipelining is essentially http keep alive. A very old jetty > thread > > > http://jetty.4.x6.nabble.com/HTTP-1-1-Request-Pipelining-handling-td18682.html > > <http://www.google.com/url?q=http%3A%2F%2Fjetty.4.x6.nabble.com%2FHTTP-1-1-Request-Pipelining-handling-td18682.html&sa=D&sntz=1&usg=AFQjCNFK8GElQKiAGxnzedN4GayjF9oHyw> > > indicates that for simplicity jetty will execute subsequent requests on > the kept-alive socket serially. > > Jonah > > > On Mon, Feb 22, 2016 at 3:33 PM, Miguel Ping <migue...@gmail.com > <javascript:>> wrote: > >> Hi guys, >> >> I'm trying to replicate an experiment on nodejs and http pipelining: >> http://blog.yld.io/2016/02/08/squeeze-the-juice-out-of-node/ >> >> This is what I got right now: >> https://gist.github.com/mping/98bb8eb9faf3c51f9889 (using >> *com.ninjudd/ring-async*) >> >> Problem is I can't get pipelining to work as in nodejs; by doing two reqs >> they are sequential, ie, the dates that I'm printing have two secs. >> Basically I want that the server prints two "identical" accpt dates, and >> the response should show that (now not working): >> >> $ tail -f reqs.txt | nc 127.0.0.1 8888 >> >> >> HTTP/1.1 200 OK >> Date: Mon, 22 Feb 2016 20:29:10 GMT >> Transfer-Encoding: chunked >> Server: Jetty(7.6.8.v20121106) >> >> 48 >> id: 1, uri: /a >> Mon Feb 22 20:29:10 WET 2016 >> Mon Feb 22 20:29:12 WET 2016 >> 0 >> >> HTTP/1.1 200 OK >> Date: Mon, 22 Feb 2016 20:29:12 GMT >> Transfer-Encoding: chunked >> Server: Jetty(7.6.8.v20121106) >> >> 48 >> id: 2, uri: /b >> Mon Feb 22 20:29:12 WET 2016 >> Mon Feb 22 20:29:14 WET 2016 >> >> >> I'm guessing that this is either my mistake with core.async or the >> adapter. >> >> Thanks >> >> -- >> You received this message because you are subscribed to the Google >> Groups "Clojure" group. >> To post to this group, send email to clo...@googlegroups.com >> <javascript:> >> Note that posts from new members are moderated - please be patient with >> your first post. >> To unsubscribe from this group, send email to >> clojure+u...@googlegroups.com <javascript:> >> For more options, visit this group at >> http://groups.google.com/group/clojure?hl=en >> --- >> You received this message because you are subscribed to the Google Groups >> "Clojure" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to clojure+u...@googlegroups.com <javascript:>. >> For more options, visit https://groups.google.com/d/optout. >> > >
-- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
