we shouldn't stuff model.py with lots of things.
also the visit class cant get simplier then that.
The original thoughs behind moving identity to the model where
- we couldn't agree on a default model
- taking things out was a pain
- people where having lots of troubles undestanding how the identity was manage "by two tables"
- its better to have it there visible then hidden in the deeps of TG
- general complains of "identity not working" due to bad configuration/not knowing the interface.
From those none applies here, well except the 2 tables thing. But what else you want from a anon user? other then went he was in, and for how long that "session is keep"
On 4/29/06, Simon Belak <[EMAIL PROTECTED]> wrote:
Ticket #803 seems interesting:
http://trac.turbogears.org/turbogears/ticket/803
Cheers,
Simon
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---
- [tg-trunk] #803 ExtendingVisitFramework Simon Belak
- [tg-trunk] Re: #803 ExtendingVisitFramework Jorge Vargas
- [tg-trunk] Re: #803 ExtendingVisitFramework Jorge Godoy
- [tg-trunk] Re: #803 ExtendingVisitFramework jvanasco
- [tg-trunk] Re: #803 ExtendingVisitFramework Jorge Vargas
