----- Ursprüngliche Nachricht ----- Von: "Dirk Ollmetzer" <[email protected]> Gesendet: 17.08.2016 21:47 An: "[email protected]" <[email protected]> Betreff: Re: [oxid-dev-general] Blog post: session handling in OXID eShop 6
Hi Marco, I would not recommend to use the normal database for session storing - particularly not in high load scenarios, because DB load is already a serious bottleneck then. Storing the Session Data in Memcache was a solid, reliable and scalable solution in a setup, I had to manage some years ago, like it is mentioned in the article. But nonetheless, thanks for the info. Regards, Dirk Am 17.08.2016 um 14:18 schrieb Marco Steinhaeuser: > Hey folks, > > if you run high load scenarios with multiple application servers, this > blog post might be interesting for you, as there will be changes in > session handling in OXID eShop 6. > > Until now, we used the regular PHP session handling and optionally, > centralized session storage for high load scenarios. In this blog post, > Gregor shows up clever alternatives and how to write an own session > handler if you want to use a database for session storage anyway: > http://oxidforge.org/en/session-handling-with-oxid-eshop-6-0.html > > Regards > > Marco > > _______________________________________________ > dev-general mailing list > [email protected] > http://dir.gmane.org/gmane.comp.php.oxid.general _______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
_______________________________________________ dev-general mailing list [email protected] http://dir.gmane.org/gmane.comp.php.oxid.general
