Brice Burgess wrote:
Juha Suni wrote:
I've seen programming leakage that resulted in session files of
several megabytes, causing some minor slowdowns, but still
functioning 100%.
A few megabyte session is a terrible thing -- and better architecture
should be investigated. I remember doing a
David Duymelinck wrote:
Putting post data in a session isn't a good choice because cookies and
sessioncookies have a limited file size.
Ermm... the session data is not stored in the cookie (thank god). Therefore
filesize for regular POST-requests should not be a problem.
Storing huge amounts
Juha Suni wrote:
I've seen programming leakage that resulted in session files of several
megabytes, causing some minor slowdowns, but still functioning 100%.
Sessions are incredibly handy and powerful, if used correctly. I'm not
recommending dumping all your data there, but you shouldn't
Juha Suni schreef:
David Duymelinck wrote:
Putting post data in a session isn't a good choice because cookies and
sessioncookies have a limited file size.
Ermm... the session data is not stored in the cookie (thank god). Therefore
filesize for regular POST-requests should not be a
Currently I use PHP's built in session functions to
handle ensuring users are logged in, etc. It doesn't
work correctly a small percentage of the time, but is
robust as far as being able to use the $_SESSION array
and other such things. Now that I'm starting to use a
bunch of jquery stuff, I'm
Kim Johnson wrote:
Currently I use PHP's built in session functions to
handle ensuring users are logged in, etc. It doesn't
work correctly a small percentage of the time, but is
robust as far as being able to use the $_SESSION array
and other such things. Now that I'm starting to use a
bunch
session handling versus PHP
Kim Johnson wrote:
Currently I use PHP's built in session functions to
handle ensuring users are logged in, etc. It doesn't
work correctly a small percentage of the time, but is
robust as far as being able to use the $_SESSION array
and other such things. Now that I'm
Kim Johnson schreef:
Currently I use PHP's built in session functions to
handle ensuring users are logged in, etc. It doesn't
work correctly a small percentage of the time, but is
robust as far as being able to use the $_SESSION array
and other such things. Now that I'm starting to use a
If you auto-fill form fields using php session and want to convert it to
a cookie-based storage
then its a good choice because you will offload your server.
Kim Johnson wrote:
Currently I use PHP's built in session functions to
handle ensuring users are logged in, etc. It doesn't
work
Thanks to all three of you for the responses :)
To explain a bit more about the extent of how I use
the sessions, the majority of why I use them is to
restrict access to certain areas. I have varying
levels of permissions on each user account, and do the
usual check if they are logged in on each
Kim Johnson wrote:
Given those exact things, do you three (or anyone
else) have an opinion on which would be better in php
or jquery? The auth, at least, will need to be almost
everywhere.
thanks,
-kim
Kim,
Keep your authentication state server side (via PHP's session). If you
do it
Kim Johnson schreef:
Thanks to all three of you for the responses :)
To explain a bit more about the extent of how I use
the sessions, the majority of why I use them is to
restrict access to certain areas. I have varying
levels of permissions on each user account, and do the
usual check if
12 matches
Mail list logo
