#spdy

All features of Nginx-1.8.1 are inherited, i.e., it is compatible with Nginx.

Dynamic module loading support (DSO). You don't have to recompile Tengine when adding new modules to it.

HTTP/2 support. The ngx_http_v2_module supersedes the ngx_http_spdy_module module.

Sends unbuffered upload directly to HTTP and FastCGI backend servers, which saves disk I/Os.

More load balancing methods, e.g., consistent hashing, session persistence, upstream health check, and resolving upstream domain names on the fly.

Input body filter support. It's quite handy to write Web Application Firewalls using this mechanism.

Dynamic scripting language (Lua) support, which is very efficient and makes it easy to extend core functionalities.

SPDY (pronounced speedy) is a now-deprecated open-specification networking protocol that was developed primarily at Google for transporting web content. SPDY manipulates HTTP traffic, with particular goals of reducing web page load latency and improving web security. SPDY achieves reduced latency through compression, multiplexing, and prioritization, although this depends on a combination of…

fast is never fast enough, when 100ms a long time

So, I’m sat looking at the PINGDOM website speed test and thinking “780ms … from Sweden… that’s not bad” but there’s this thing….

I thought PINGDOM used HTTP/2, I’m wrong but I did think that. Which made the amount of SSL setup this is doing seem quite high. There’s SSL connection establishment overhead for multiple objects which, historically, has always been an objection to SSL web pages. And,…