On 05/21/2013 11:55 AM, Reindl Harald wrote:
having a customized session handler *mandatory* is dumb damned it *creates additional load* where zero load is by disk IO and by CPU cycles for php code
in the first front scaleable is how many users can i serve and with my setup i can serve much more than with a mysql session handler which prodcues IO loads
I guess what Cor means here is that you can add multiple webservers to your cluster which all share the same session information (because it would be stored in MySQL and not on a local ramdisk on each separate server).
You say that you can serve "much more" users with your setup compared to a MySQL session handler. Can you give any indication about how "much more" users we are talking about? Do you have some test results? This discussion is getting nowhere without solid ground for such allegations.
The Roundcube dev's have made it clear why they chose to handle sessions through a database. Until now, your main complaints have been that your custom garbage collection system doesn't work for Roundcube (well, make it so then...), that it doesn't honor your PHP configuration settings and furthermore you argue that a MySQL session handler would cost a lot of performance (compared to traditional PHP session handlers), for which you haven't provided any evidence so far.
Please, do the rest of this list a favor and do provide some real evidence for the claims you raise or stop behaving like a troll. Thanks.
Geert