I agree that we should have one place to store how the identity
variables (such as fieldname) are stored.  I'm not to sure on how to
do this at the moment, but I will think about it.

for the time being, I have defined the config variables which I noted
earlier, and they are part of the current template in tg.devtools.

-chris

On May 30, 3:28 pm, Patrick Lewis <[EMAIL PROTECTED]> wrote:
> On May 30, 2:13 pm, percious <[EMAIL PROTECTED]> wrote:
>
> > i am not sure cookie name and name of the login controller are really
> > identity entities.  (say that 3 times fast!)
>
> My only real (badly made) point is that I think the config/
> middleware.py template should use the config values you are defining.
> All I see being used there is User, but the value for User shouldn't
> be imported from model, it should use this config. Otherwise, people
> have two make two changes if they want to change the underlying User
> class. Perhaps all this that goes without saying.
>
> Other config values may need to be defined for tgrepozewho to use
> (I've listed some, there may be others). I imagine they probably go in
> the global config.  Maybe it doesn't get handled now.  But you are
> touching a global config item called 'identity', so it's something to
> think about.
>
>
>
> > what do you mean by login form values?
>
> The login form field names for the user_name and password, and the
> name of the submit button.
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to