On 1/10/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > 1132 and 1164 both provides solutions for the CurrentUser issue), but > as > of now, these solutions have been (in my own opinion rightly) deemed > too > hackish to get committed. This thread is aimed at finding a clean > implementation of those two concepts. > Obviously, the solution _will_ introduce some coupling between the data > layer and the request layer (well, who knows ?). The point is mainly to > make it as light as possible.
I wrote both patches. Please just ignore #1132. It sucks. I was pretty much just trying to start a conversation there with the simplest (in this case least amount of code) thing I could get to work. (I probably should have done so on the list) #1164 is better IMHO, but I still don't like it too much. I got the context processor ideas from rjwittams. I think he's still on vacation, but I'd love to hear how close I came to what he was imagining. What do people think about the context processor idea? Not necessarily this implementation, but just the idea of a generic context (just a dict in the simplest case) that gets passed in to the manipulator for access by fields. AFAICT this is where the "coupling" is happening. Any other ideas on how a field might get access to the current user? Joseph
