> > advise against having some data
> > replicated and other data not replicated,
> > depending on whether it's in a CFC
> > instance or not.
>
> What's your reasoning behind that?
It seems to me that you should either have session replication, or you
shouldn't. If you replicate some things, but not others, how will you deal
with those cases? If a page uses one session variable that contains a simple
value, and uses another session variable that contains a CFC instance, how
would you resolve that if the data isn't actually all in the same scope?
> > I don't know of any way using JRun
> > clustering to enforce "sticky" sessions -
> > that's typically done with web server
> > clustering by having the cluster manager
> > issue a cookie at each initial request,
> > and redirect future requests to each
> > server depending on the cookie value.
>
> That's too bad that Jrun can't sticky the sessions. So is
> it your recommendation to get a clustering device/load balancer,
> use sticky sessions and only cluster a minimal set of data
> across servers?
As Dave Carabetta helpfully pointed out, just because I don't know about
something doesn't mean it can't be done:
http://www.bpurcell.org/blog/index.cfm?mode=entry&entry=986
I'm a bit confused after reading that, though. The article says that the
default with JRun is to have sticky sessions. It also says that you should
use sticky sessions if you're using session replication, which doesn't make
any sense to me.
Dave Watts, CTO, Fig Leaf Software
http://www.figleaf.com/
voice: (202) 797-5496
fax: (202) 797-5444
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
