Hmm.. does the AWS allow you to flush the output buffer to the HTTP client from time to time? That would help for the "forever iframe" type of comet implementations.
I quickly glanced at the docs and don't see anything that lets you access the lower level guts of the HTTP response. Of course, Apache out of the box doesn't work well w/ long-lived or persistent connections. I can't speak for LigHTTP. But assuming those problems are solved, it seems we still have the obstacle of being able when to flush the buffer when we need to. _______________________________________________ Rails-spinoffs mailing list Rails-spinoffs@lists.rubyonrails.org http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs
