|
|
Posted by Balazs Wellisch on 10/06/23 11:37
> The loadbalancingpart is however irrelevant if you use a database for
> sessionstorage, since every session will contact the same database that
> stores the sessions.
> (If you plan to use more databases for sessionstorage, I give up. :P)
Yeah, the obvious solution is to store all the session information in a
single database. But that would limit the failover capability of the system.
I was thinking about setting up each box with its own copy of the database
and replicate the data between each one. However, I don't think this is a
feasible solution since session info changes all the time and I can't have
the dbs continuously replicate themselves all the time. I suppose I could
use sticky sessions, but I was wondering if there was a better solution out
there.
> A good place to start is at ZEND:
> http://www.zend.com/zend/spotlight/code-gallery-wade8.php
>
Yes, I looked at Zend and I'm considering investing in their technology.
> That page contains a good example, but without sessionlocking.
> I wrote my own that does implement sessionlocking. It is not tested 100%,
> but seems to work great so far. If you are interested I'll publish it on
> the net, but just start with zend. :-)
>
I'm definitly interested and I'm sure others would benefit from your work as
well. Please let us know if you do decide to publish it!
Thanks,
Balazs
Navigation:
[Reply to this message]
|