On Tue, Dec 14, 2010 at 12:54 PM, Alice Bevan–McGregor
wrote:
>
> An application is an application and servers are imagined but not actually
>> concrete.
>>
>
> Could you elaborate? (Define "concrete" in this context.)
WSGI applications never directly touch the server. They are called by the
Ian,
It's not clear to me how this can be composed or abstracted.
Filters themselves have no knowledge of the applicaiton, in a similar
vein to middleware not knowing if the next layer in the onion skin is
the final application, or another bit of well-behaved middleware,
except that filters
On Sun, Dec 12, 2010 at 9:59 PM, Alice Bevan–McGregor
wrote:
> Howdy!
>
> There's one issue I've seen repeated a lot in working with WSGI1 and that
> is the use of middleware to process incoming data, but not outgoing, and
> vice-versa; middleware which filters the output in some way, but cares no
