Re: [PATCH] Add rack.after_reply functionality

[Blake Williams <blake@blakewilliams.me>]

> OK.  Keep in mind this can be server-dependent since unicorn
> can't support persistent connections while (most?) other servers
> do (and they may disable TCP_CORK or Nagle, etc).

I see, I’ll look into this as well.

>>> Citation(s) needed.  Also, are there any proposal(s) to get this
>>> into the Rack specification?
>> 
>> Not that I’m aware of. But I agree that it and early_hints could both be
>> good additions to the spec.
> 
> By "Citation(s) needed", can you list some other (preferably
> well-known) Rack servers which also implement this feature?
> 
> We wouldn't want current unicorn users thinking we're adopting
> random new things which nobody else supports :>
> 
> Thanks.


Totally understood. I looked at Puma, Thin, and Webrick and only Puma
supports this functionality without a third-party gem. There is at least one
third party gem adding this functionality to web servers that don’t support it,
but it doesn’t look like it’s being maintained any longer.

I briefly dove into the Puma source and it looks like rack.after_reply has
been supported since 2011. It’s also still in use by Puma for their common 
logger middleware patch.