Comment 4 for bug 148214

> I think the right way to do is to take application and session
> parameters as argument to Session.__init__ and add a processor to the
> application instead of loadhook.

That's indeed what I've done so far.

In addition, I am moving most of the functionality out of the session object itself and into the processor (which is a class implementing __call__).

> Session can be extended from ThreadedDict instead of Storage to store
> session data for every request instead of creating a new session
> object for every request.

That's an excellent idea!