|
|
Posted by Peter Fox on 01/07/06 11:07
Following on from Balazs Wellisch's message. . .
>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.
[The first time I've ever considered this issue so don't take it as
tried-n-tested]
Surely /each box/ doesn't need /its own/ database. If the objective is
to allow some failure to be brushed-off then two databases with
replication should do the trick when you need both DBs to be u/s before
the system fails. Also you would operate normally on a single DB with
the other in standby - as you'd be operating presumably with your main
DB.
Q: What happens if I log into your site twice from my Tabbed browser.
Might I operate as the same session but hitting different servers?[1]
If so what exploit could I use to load a trolley on both screens, buy on
one and decide not to buy on the other and have the cancel overwrite the
buy but not before the goods were authorised for dispatch. [Not a 'you
mustn't do it!, but a GLB-ism]
[1] Even if by hacking the browser (but more likely by cutting and
pasting ?SID=123456 from one tab to the other) - could be worth a lot of
money.
--
PETER FOX Not the same since the icecream business was liquidated
peterfox@eminent.demon.co.uk.not.this.bit.no.html
2 Tees Close, Witham, Essex.
Gravity beer in Essex <http://www.eminent.demon.co.uk>
Navigation:
[Reply to this message]
|