On 17/03/12 09:10, Fabrizio Bertocci wrote: > To limit the load on the server and reduce the number of calls to the > database, I was wondering if somebody (Matt?) can help me understanding > if it is safe to 'cache' the auth state (or, since it's already present > in ses.authstate, reuse that value) and send back immediately the > previous auth state.
Alternatively, have you considered caching the public key fetched from the database for a short period? How close together are these re-auths? There may be very good reasons for not caching, I'm no expert, just throwing up ideas. Regards, -- Stuart Longland (aka Redhatter, VK4MSL) .'''. Gentoo Linux/MIPS Cobalt and Docs Developer '.'` : . . . . . . . . . . . . . . . . . . . . . . .'.' http://dev.gentoo.org/~redhatter :.' I haven't lost my mind... ...it's backed up on a tape somewhere.
