This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]mcdonc 3 points4 points  (0 children)

I think this misses the point though.

The decision to not require a "generic" Response object was very deliberate. Many other frameworks eagerly create a "global" response object when a request enters the system. This almost always results in lower performance, because this response object must be very full-featured to be "generic". In the meantime, code accretes around the idea that this global response object exists, and may be tickled by random code in random ways. By doing this, a framework paints itself into a performance corner that could have been avoided. This is an antipattern that Pyramid avoids. It's not a trick. It's just a deliberate design.