Sticky IP is a mechanism employed by many hardware load balancers to keep a
session tied to a specific computer. Imagine you had a cluster of computers
(numbered 1 to 5), the hardware load balancer is supposed to send traffic to
whichever of those boxes is best suited to handle the request (it does this
by monitoring response times, and stuff like that). This works fine if all
you are doing is serving content and don't care which machine it comes from,
but what if you are using session state management (which is usually in
memory on a specific PC)? Then you could end up with different requests
being processed by different boxes - so put an item in a shopping cart (on
computer 1) and a second later it is gone because you are now on another box
(maybe computer 2). Sticky IP addresses this issue by ensuring that once a
session is started all requests made by that client IP address go to the
same box.
This is why ColdFusion CLIENT variables are of value, they allow session
data to be shared across multiple boxes, meaning you'd not have to resort to
using sticky IP.
--- Ben
-----Original Message-----
From: Kola Oyedeji [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, July 25, 2001 11:22 AM
To: CF-Server
Subject: RE: Using CFAPP and inactive interfaces...
This is all very interesting could someone explain to me what you mean by
sticky sessions?
Cheers
Kola Oyedeji
Web developer
Allaire Certified ColdFusion Developer
http://www.ekeda.com
0208-429-7323
> -----Original Message-----
> From: Mike Fleming [mailto:[EMAIL PROTECTED]]
> Sent: 25 July 2001 15:36
> To: CF-Server
> Subject: RE: Using CFAPP and inactive interfaces...
>
>
> And what is wrong with high end load balancing ;) I've written apps
> that work fine across multiple servers with sticky sessions, with
> zero problems. Most were done with using a Local Director with
> sticky sessions.
>
> ---- Original Message ----
> From: [EMAIL PROTECTED]
> To: [EMAIL PROTECTED],
> Subject: RE: Using CFAPP and inactive interfaces...
> Date: Thu, 26 Jul 2001 00:23:19 +1000
>
> >And I would guess that this is all situated on one server, now what
> >will
> >happen when this load gets too much and you need to add an extra
> >server.
> >Using session variables means you need to then be tied to high end
> >load
> >balancing, or stick session scenarios.
> >
> >Using the client scope instead makes it easier for not only the
> >scaling
> >of the servers, but means you don't need to revisit the code and
> >rewrite
> >this code.
> >
> >
> >> -----Original Message-----
> >> From: Herman Cremer [mailto:[EMAIL PROTECTED]]
> >> Sent: Wednesday, 25 July 2001 11:51 PM
> >> To: CF-Server
> >> Subject: RE: Using CFAPP and inactive interfaces...
> >>
> >> I have developed a whole stack of stuff
> >> using session variables.
> >>
> >> Like an online accounting system with
> >> 100+ users at a time, bashing away 12 hours a day.
> >>
> >> Never had a single problem.
> >>
> >> As far as I'm concerned....session vars works
> >> very good.
> >>
> >>
> >> Herman
> >
> >
> >
> >
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
------------------------------------------------------------------------------
To unsubscribe, send a message to [EMAIL PROTECTED] with
'unsubscribe' in the body or visit the list page at www.houseoffusion.com
