On Tuesday, April 3, 2018 at 10:20:41 AM UTC-4, AlighaThor wrote:
>
> I would do not perform the database check in every request (and I think
> Massimo did'nt mean that :)), only during the the second (or more) attempt
> to log in with the same user.
>
> Let's say you have the X user logged in.
I would do not perform the database check in every request (and I think
Massimo did'nt mean that :)), only during the the second (or more) attempt
to log in with the same user.
Let's say you have the X user logged in. You stored the uuid in the
auth_user.uuid field as mentioned. Then in
On 12/03/2018 15:08, Anthony wrote:
What if I cache on disk the result of a function that returns the
session id and I check if it corresponds to the real value?
Not sure what you mean. Where does the session ID produced by the
function come from, and how is the "real value"
On Monday, March 12, 2018 at 7:23:26 AM UTC-4, Manuele wrote:
>
> Il 07/03/18 15:51, Anthony ha scritto:
> > Be aware, that will require a database select on every request. If you
> > want to minimize the database hits, you could also store in the
> > session the time of the last database
Il 07/03/18 15:51, Anthony ha scritto:
> Be aware, that will require a database select on every request. If you
> want to minimize the database hits, you could also store in the
> session the time of the last database lookup, and then only check the
> database every X minutes (the tradeoff being
Thanks a lot Massimo! As precious as ever.
:)
M.
On 07/03/2018 07:02, Massimo Di Pierro wrote:
it is possible.
when a user first logs in, store a uuid in the session and write it in
the database (in a new custom field in the auth_user table). When a
request arrives if the uuid in the
6 matches
Mail list logo
