mmcgr...@redhat.com wrote:
>
> On Mar 14, 2009, at 8:27 PM, Nigel Jones wrote:
>
>>
>> - "Toshio Kuratomi" wrote:
>>
>>> ricky and I have identified a piece of code in fas2's new
>>> safasprovider
>>> that's querying the database a lot. It's causing anything that
>>> checks
>>> identity to
On Mar 14, 2009, at 8:27 PM, Nigel Jones wrote:
- "Toshio Kuratomi" wrote:
ricky and I have identified a piece of code in fas2's new
safasprovider
that's querying the database a lot. It's causing anything that
checks
identity to issue a query to the database to lookup the visit cookie
- "Toshio Kuratomi" wrote:
> ricky and I have identified a piece of code in fas2's new
> safasprovider
> that's querying the database a lot. It's causing anything that
> checks
> identity to issue a query to the database to lookup the visit cookie.
> This is causing things that lookup infor
I'm out, sorry for the top post. But zodbot FAS routines are not
functional due to this, so I'd be +1 here if I had a vote :)
On 3/14/09, Ricky Zhou wrote:
> On 2009-03-14 05:36:27 PM, Toshio Kuratomi wrote:
>> Ricky and I have both looked at the code in
>> fas/safasprovider.py::SaFasIdentity and
On 2009-03-14 05:36:27 PM, Toshio Kuratomi wrote:
> Ricky and I have both looked at the code in
> fas/safasprovider.py::SaFasIdentity and think that it's safe to cache
> this. The TG-1.0.8 saprovider on which safasprovider is based does not
> cache this but I've looked at the code and it seems lik
ricky and I have identified a piece of code in fas2's new safasprovider
that's querying the database a lot. It's causing anything that checks
identity to issue a query to the database to lookup the visit cookie.
This is causing things that lookup information on the identity multiple
times to take
