Sebastian wrote:
15 or 150k or even more should not a problem for an ISP providing database servers to his customers
but it's per user and i f.e. store those sessions in ram (only used while browser is open).
session file needs to be loaded every time - so why not move as most as possible into this file and try not to load additional files like config.inc.php, themes with every request.
on a well configured system that should already be done by disk cache.
Juergen --------------------- provider spam: ______________________________________________________________ Verschicken Sie romantische, coole und witzige Bilder per SMS! Jetzt bei WEB.DE FreeMail: http://f.web.de/?mc=021193
Juergen Wind schrieb:
Sebastian wrote:
15 or 150k or even more should not a problem for an ISP providing database servers to his customers
but it's per user and i f.e. store those sessions in ram (only used while browser is open).
yes per user, of course
you store this session in ram? you will say you do not use the default php session handler 'file'?
and? whats wrong with this?
what do you think exactly should not be stored in session and why?
session file needs to be loaded every time - so why not move as most as possible into this file and try not to load additional files like config.inc.php, themes with every request.
on a well configured system that should already be done by disk cache.
same for session file