Funny, but a one connection at a time restriction would break gifsockets just like long polling.
Dude, the gifsockets example "uses one connection at a time" because I'm too lazy to implement a server using Netty or Aleph in Clojure. The only important part from the gifsockets concept is writing gif frames on demand. The rest is up to you
gifsockets is just a niche implementation of long polling. They work the same way.
Ups… I read the wrong thing then. I thought the guy was referring to the sample gifsockets app that now supports only one connection at a time. Cheerio!