Identity does the following for *every* HTTP request that is handled by TurboGears (CherryPy):

load the user's secret token
load the user record and compute the user's groups and privileges
update the user's secret token expiration date

One of the things I'm thinking of doing is modifying the current SqlObjectIdentityProvider to use SQL statements rather than SQLObject directly. I would expect this to be *much* faster.

I don't know what priority Kevin puts on this, but I'm willing to make this a post 0.9 or even post 1.0 fix. (I'm a little busy at the moment.)


On 31 Dec, 2005, at 5:09 am, Davide Bertola wrote:


The same page with the same template
takes 0.4/0.5 seconds more if you are a logged user.

For an unlogged user the whole page tales 0.2 sec
and it uses the database more than identity may need.

You can see that if I'm online : http://dade.ath.cx:8080/
refreshing many times and logging with "foo"/"bar"

(Powerbook G4 1ghz, sqlite database)


--

Jeff Watkins

http://newburyportion.com/


"Just because you have the right to do something, doesn't mean it's the right thing to do."

-- Fred Friendly, former president of CBS News



Reply via email to