Hi Ben,
I'm going to implement your patch, but I'd like to cut down the number
of additional config settings. The number of parameters is already
scaring enough ;-) What do you think about:
1) Assuming that the class name is always the same as the module name
(this is also backward compatible
Yes that would work fine for our app.
Agreed about too many config settings - I thought about having the
Session / SessionStore set through some kind of runtime configuration.
Allow each context to set its own session/store combo perhaps? but that
is a larger effort, and I didn't need that
Ok, this is now in the trunk if you want to check it out.
Ben Parker wrote:
Agreed about too many config settings - I thought about having the
Session / SessionStore set through some kind of runtime configuration.
Allow each context to set its own session/store combo perhaps? but that
is a
