>Unicorn didn't use Rack.env in a thread safe way. Was Unicorn itself not thread safe? It sounds like Unicorn had the requirement that once you send back the r

>Unicorn didn't use Rack.env in a thread safe way. Was Unicorn itself not thread safe? It sounds like Unicorn had the requirement that once you send back the request to the user you must stop accessing the request object. Maybe Unicorn didn't document that requirement clearly, but even if it's not documented it's not clear to me that Unicorn itself is not thread safe, but rather that it has undocumented pitfalls that can easily lead to thread unsafety.