|
Use a centralized shopcart.....
I suggest you look into
a.) client side shop cart
or
b.) centralized webserver-independent shop cart storage
there is now way that you are going to fix the aol proxy/multiple server
problem (short of the cheeze in the Persistence documentation which
indicates the solution is go bind entire networks to specific boxes... this
will work for most, but does not SOLVE the problem of server affinity, it
is merely a quick hack)... so I suggest you stop looking at how to force
server affinity and start looking at centralized shopping carts.. NFS
mount, Database driven, etc.. something RealServer Independent..
Jeremy
At 11:37 AM 4/27/00 -0700, Wayne wrote:
I have found that there is a problem for using LVS persistent modes
to handle AOL customers during load balancing. We have about
30% customers are from AOL. However, AOL has each user
goes out to fetch a page through several cache proxy servers.
I could see that one user gets a page that has a few gif files is
by getting the html code from cache-rg07.proxy.aol.com, the next
gif file from cache-rg04.proxy.aol.com, the next gif file from
cache-rg05.proxy.aol.com,... So the source IP address for even
a single page is not consistent. The next page html code is from
another cache proxy server, not predictable. The result is that a
few AOL customers saying that their shopping carts has inaccurate
items as they shopping along. the result of that is I stopped
using the shopping cart.
Is there any way to address this AOL customers' problem?
The persistent mode needs to be able to load balancing based on
the actual browser, somehow.
|
